any objection to a wide-sweeping "unifdef-y" -> "header-y" change?
given that the Kbuild "unifdef-y" directive was tagged as obsolete
in favour of "header-y" well over a year ago, any objection to just standardizing everything on header-y and removing all support for unifdef-y?
is there any compelling reason to *not* do that?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday
========================================================================