From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Can you please pull percpu#for-next into linux-next?
Date: Fri, 19 Jun 2009 11:40:35 +0900 [thread overview]
Message-ID: <4A3AFAA3.4080607@kernel.org> (raw)
Hello,
What do I need to do to get a tree pulled into linux-next rounds? The
tree in question is
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
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.
Also, is there some guide I can read about linux-next?
Thanks.
--
tejun
next reply other threads:[~2009-06-19 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 2:40 Tejun Heo [this message]
2009-06-19 3:23 ` Can you please pull percpu#for-next into linux-next? Stephen Rothwell
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=4A3AFAA3.4080607@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).