linux-kernel - Re: [GIT] kbuild

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: <20090419234501.GA6475@uranus.ravnborg.org>
Date:	Mon, 20 Apr 2009 01:45:01 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Paul Mundt <lethal@...ux-sh.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Russell King <rmk+lkml@....linux.org.uk>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [GIT] kbuild

On Mon, Apr 20, 2009 at 07:39:59AM +0900, Paul Mundt wrote:
> On Sun, Apr 19, 2009 at 11:25:55AM +0200, Sam Ravnborg wrote:
> > We have on the lists recently discussed two features:
> > 1) Move generated files to include/generated
> > 2) Introduce support for subdir-ccflags-y
> > 
> > Both features has low risk of introducing regressions
> > and including them now allow us to use the features for next
> > merge window.
> > 
> > This will for example allow arm to support mach-types.h in
> > include/generated without touching files outside arch/arm.
> > 
> This applies to sh also, although apparently I've missed the discussion
> about how mach-types.h generation should be using this.

You will soon see a path from me where I fix sh too.

	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/