Re: why is there still so much __KERNEL__ testing in include/uapi/?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 27, 2016 at 12:08:09PM -0400, Robert P. J. Day wrote:
> 
>   continuing down this road of exporting kernel headers, under
> include/uapi/ (and mostly further under linux/), there's still a *ton*
> of testing of the __KERNEL__ preprocessor check.
> 
>   now, i realize that when one does "make headers_install", all those
> files are run through "unifdef" to sanitize almost all of that kernel
> content, so it's not like it hurts, but is there any reason so much of
> it is still there? wouldn't it be tidier to get rid of it?

No, because not all of the information in those .h files should be
exported to userspace.  You could either split the files all up into two
different ones, or just live with the existing infrastructure we have.
We chose the easy one :)

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux