public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	lkml <linux-kernel@vger.kernel.org>,
	ARM kernel mailing list  <linux-arm-kernel@lists.infradead.org>
Subject: Re: Another tree for "next"
Date: Mon, 10 Sep 2012 11:52:14 -0600	[thread overview]
Message-ID: <504E28CE.6020103@wwwdotorg.org> (raw)
In-Reply-To: <m31ui9g4ff.fsf@intrepid.localdomain>

On 09/10/2012 11:42 AM, Krzysztof Halasa wrote:
> Stephen Rothwell <sfr@canb.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@kernel.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.

  reply	other threads:[~2012-09-10 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3obli3j7a.fsf@intrepid.localdomain>
     [not found] ` <20120910100144.dcbe2715cde0fea51345a354@canb.auug.org.au>
2012-09-10 17:42   ` Another tree for "next" Krzysztof Halasa
2012-09-10 17:52     ` Stephen Warren [this message]
2012-09-10 23:26       ` Stephen Rothwell
2012-09-18 10:32         ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=504E28CE.6020103@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox