linux-kernel - Re: ARM platform trees (was: Re: HTC Dream aka. t-mobile g1 support)

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: <20090722205551.GB1575@n2100.arm.linux.org.uk>
Date:	Wed, 22 Jul 2009 21:55:51 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Kevin Hilman <khilman@...prootsystems.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	David Miller <davem@...emloft.net>, swetland@...gle.com,
	pavel@....cz, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
	rlove@...gle.com
Subject: Re: ARM platform trees (was: Re: HTC Dream aka. t-mobile g1
	support)

On Wed, Jul 22, 2009 at 10:54:06AM -0700, Kevin Hilman wrote:
> Russell King - ARM Linux <linux@....linux.org.uk> writes:
> 
> > On Thu, Jun 11, 2009 at 01:54:42PM +0100, Alan Cox wrote:
> >> Make your tree the core ARM code only, any other patches you don't
> >> accept. Aggressively push stuff out to platform code, and if people want
> >> to change core code "because our platform is different" make them extract
> >> it into the platform layer not carry it in the core bits.
> >
> > I'm all for giving this a try after this merge window is over.
> 
> So, in preparation for the next merge window...
> 
> Is there an official way for ARM platform maintainers like myself to
> get stuff merged via Linus' tree?  Is simply sending a pull request to
> Linus/LKML all that's required?

Yup.
--
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/