<p dir="ltr">Hi,<br>
Header files under include/net are for kernel internal use.<br>
Header files under include/uapi are for exposure to userspace:<br>
<a href="http://lxr.free-electrons.com/source/include/uapi/">http://lxr.free-electrons.com/source/include/uapi/</a><br><br></p>
<p dir="ltr">Regards,<br>
Rami Rosen<br>
<a href="http://ramirose.wix.com/ramirosen">http://ramirose.wix.com/ramirosen</a></p>
<div class="gmail_quote">בתאריך 28 במרץ 2016 18:04, "Manoj Nayak" <<a href="mailto:manojnayak2005@gmail.com">manojnayak2005@gmail.com</a>> כתב:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>> 1) Is it possible to write a new protocol for linux with an out of<br>> tree module without modifing socket.h file?<br><br>I think this has been already tried in the following code.<br><br><a href="http://lxr.free-electrons.com/source/include/net/bluetooth/bluetooth.h#L36" target="_blank">http://lxr.free-electrons.com/source/include/net/bluetooth/bluetooth.h#L36</a><br><br><a href="http://lxr.free-electrons.com/source/include/linux/socket.h#L239" target="_blank">http://lxr.free-electrons.com/source/include/linux/socket.h#L239</a><br><br>The challenge is to expose this development specific header file to userspace.<br>The following document talks about that.<br><br><a href="http://kernelnewbies.org/KernelHeaders" target="_blank">http://kernelnewbies.org/KernelHeaders</a><br><br></div>Regards<br></div>Manoj Nayak<br><div><div><br></div></div></div>
<br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div>