linux-kernel - Re: [GIT PULL] kbuild updates for 2.6.33

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: <20091209192038.GA7827@merkur.ravnborg.org>
Date:	Wed, 9 Dec 2009 20:20:38 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Michal Marek <mmarek@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [GIT PULL] kbuild updates for 2.6.33

On Wed, Dec 09, 2009 at 09:31:08AM -0800, Randy Dunlap wrote:
> On Wed, 9 Dec 2009 10:33:49 +0100 Michal Marek wrote:
> 
> > On Tue, Dec 08, 2009 at 02:30:04PM +0100, Michal Marek wrote:
> > > Hi Linus,
> > > 
> > > these are the kbuild patches I collected for 2.6.33. There might be a few
> > > more later, but this is the main part.
> > > 
> > > Thanks,
> > > Michal
> > > 
> > > The following changes since commit 6ec22f9b037fc0c2e00ddb7023fad279c365324d:
> > >   Linus Torvalds (1):
> > >         Merge branch 'x86-debug-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://repo.or.cz/linux-kbuild.git for-next
> > 
> > Hi Linus,
> > 
> > The kbuild tree now breaks with 250cce26 ("iwlwifi: driver version
> > track kernel version") which you merged yesterday. Stephen Rothwell
> > kindly provided a fix, which I would normally apply to the kbuild tree,
> > but I don't want to rebase it as I already sent the pull request. Could
> > you please apply the following one-liner when merging the kbuild tree?
> > Thanks!
> 
> Hi > Michal,
> 
> Is there anything that tells us when we should/must use
> <generated/*.h> ?

The original idea was that include/generated/ should
be used for all generated header files.

I once had a patch applied that used it for other
generated files - this was a bad idea. Said patch
was reverted as it had much bigger issues.

So think of it as a place for generated header files only.
This also warrants the location in include/

But only for 'global' header files. For drivers
and the like that needs the header file only locally the
header file should not be located n include/generated,
as it is only for the global headers.

asm-offsets.h is a good example here.

	Sam
--
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/