why is there still so much __KERNEL__ testing in include/uapi/?
Robert P. J. Day
rpjday at crashcourse.ca
Fri May 27 12:08:09 EDT 2016
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?
or is there some rationale for leaving it there?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
More information about the Kernelnewbies
mailing list