linux-kernel - Re: [patch v2 01/35] Hexagon: Add generic headers

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] [day] [month] [year] [list]

Message-ID: <1400760.2CJ9v55MlQ@wuerfel>
Date:	Wed, 31 Aug 2011 22:00:41 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	David Brown <davidb@...eaurora.org>
Cc:	Richard Kuo <rkuo@...eaurora.org>, linux-kernel@...r.kernel.org,
	linux-hexagon@...r.kernel.org
Subject: Re: [patch v2 01/35] Hexagon: Add generic headers

On Wednesday 31 August 2011 12:51:11 David Brown wrote:
> On Wed, Aug 31, 2011 at 03:24:42PM +0200, Arnd Bergmann wrote:
> > On Tuesday 30 August 2011, Richard Kuo wrote:
> > > Reworked to use the Kbuild generic headers mechanism.
> > > 
> > > Signed-off-by: Richard Kuo <rkuo@...eaurora.org>
> > 
> > Acked-by: Arnd Bergmann <arnd@...db.de>
> 
> Any suggestions on what path this code should flow to get into the
> kernel?

It should get into linux-next now and then get submitted directly to
Linus at the start of the merge window.

I'm happy to take anything that concerns hexagon and arm likewise into
the arm-soc tree.

While I am the de-facto gatekeeper for new architectures, I have not
seen a reason to start a consolidated minor-architectures tree to collect
these.

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