linux-kernel - Re: [RFC] ARM Subarchitecture group maintainership

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.2.00.1105182234130.14430@xanadu.home>
Date:	Wed, 18 May 2011 22:42:09 -0400 (EDT)
From:	Nicolas Pitre <nico@...xnic.net>
To:	Barry Song <21cnbao@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Russell King <linux@....linux.org.uk>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] ARM Subarchitecture group maintainership

On Thu, 19 May 2011, Barry Song wrote:

> does it mean if we want to add a new SoC plat/mach, we will send
> patches againest this tree?

Yes.  Or against latest mainline tree from Linus.

> will this tree merge into rmk's tree? then rmk's tree will only manage
> arm common codes?

Something like that.  The exact details will be fleshed out as we go. 
The idea is to give a round of review from a higher point of view to 
make sure no opportunities for code reuse is missed, etc.  The mechanics 
of how this code transitions from this tree into mainline during the 
merge window is secondary.


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