linux-kernel - Re: Another tree for "next"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 10 Sep 2012 11:52:14 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Krzysztof Halasa <khc@...waw.pl>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	lkml <linux-kernel@...r.kernel.org>,
	ARM kernel mailing list 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Another tree for "next"

On 09/10/2012 11:42 AM, Krzysztof Halasa wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
> 
>>> could you please add the following to your "next" tree?
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git  branch: next
> 
>> Could you be a bit more clear about what will be in that tree, please?
>> Also when you repost this request, please post it a bit more widely among
>> other people/lists who may be interested in this work.  Remember that
>> linux-next is really only for stuff that is ready for Linus to pull into
>> the next merge window (or bug fixes).  Also, would this tree be pulled
>> directly by Linus, or via some other tree?
> 
> My plan is to merge all the stuff I'm (eventually) working on in the
> above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to
> Linus

ARM-SoC-related pull requests should be sent to the arm-soc tree, who
will then aggregate all the ARM-SoC-related changes and issue pull
requests to Linus.

That is, arm@...nel.org, plus the Linux ARM kernel list CC'd.

The patches would also need to be sent to the Linux ARM kernel list (and
any other relevant lists) before being applied to your tree.

ARM core changes would likely go through Russell King's tree, perhaps
depending on what dependencies they have.
--
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/