From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: linux-next@vger•kernel.org, Ingo Molnar <mingo@elte•hu>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: Can you please pull percpu#for-next into linux-next?
Date: Fri, 19 Jun 2009 13:23:28 +1000 [thread overview]
Message-ID: <20090619132328.95ee96bc.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A3AFAA3.4080607@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Hi Tejun,
On Fri, 19 Jun 2009 11:40:35 +0900 Tejun Heo <tj@kernel•org> wrote:
>
> What do I need to do to get a tree pulled into linux-next rounds? The
> tree in question is
You need to ask. :-)
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-next
> http://git.kernel.org/?p=linux/kernel/git/tj/percpu.git;a=shortlog;h=for-next
You also need to give me the name(s) of people to inform about any issues
I have with the tree (defaults to you).
> and contains percpu related changes scheduled for the next (2.6.32)
> merge window. The tree touches a lot of archs and percpu users so
> it'll probably cause some headache during the devel cycle.
Since it is for 2.6.32, I will only add it after 2.6.31-rc1 is released.
What I tell everyone: all patches/commits in the tree/series must
have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
> Also, is there some guide I can read about linux-next?
There is a web site which is mostly useful:
http://linux.f-seidel.de/linux-next/pmwiki/
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-19 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 2:40 Can you please pull percpu#for-next into linux-next? Tejun Heo
2009-06-19 3:23 ` Stephen Rothwell [this message]
2009-06-19 3:44 ` Tejun Heo
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=20090619132328.95ee96bc.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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