From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Another tree for "next"
Date: Mon, 10 Sep 2012 19:42:44 +0200 [thread overview]
Message-ID: <m31ui9g4ff.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20120910100144.dcbe2715cde0fea51345a354@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 10 Sep 2012 10:01:44 +1000")
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, and (from time to time) WAN network drivers pulled by Dave. BTW
this includes both current fixes (for "this") and true "next" changes.
All of this is low profile and will be frequently empty.
Hope that's ok. Alternatively I can add separate trees/branches
(currently I'm only working on IXP4xx, at least as far as we're talking
about pullable git trees). Just wanted to minimize effort needed on
your side.
Not sure about these other people/lists, added lkml.
--
Krzysztof Halasa
next parent reply other threads:[~2012-09-10 17:42 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 ` Krzysztof Halasa [this message]
2012-09-10 17:52 ` Another tree for "next" Stephen Warren
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=m31ui9g4ff.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--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