linux-kernel - Re: why so many unexported headers checking __KERNEL_

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.00.0803260922420.6408@localhost.localdomain>
Date:	Wed, 26 Mar 2008 09:23:43 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: why so many unexported headers checking __KERNEL__?

On Wed, 26 Mar 2008, David Woodhouse wrote:

> On Wed, 2008-03-26 at 09:16 -0400, Robert P. J. Day wrote:
> > well, since i already have the output from my script, i might toss
> > together some per-directory patches to start removing some of
> > that. this sounds more like a one-shot thing than adding permanent
> > checking to the build process.
>
> Makes sense.
>
> Remember, one of our goals is to move towards having files which are
> just _copied_ (header-y) instead of having these ifdefs. If, in your
> travels, you see a way you can split headers up more sensibly to
> achieve that, it would be good.

that might be harder to encode into a script.  :-)

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/