From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: Rusty Russell <rusty@rustcorp•com.au>,
Christoph Lameter <cl@linux-foundation•org>,
Ingo Molnar <mingo@elte•hu>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: manual merge of the percpu tree with Linus' tree
Date: Mon, 7 Sep 2009 20:24:20 +1000 [thread overview]
Message-ID: <20090907202420.c0bd57e5.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4AA4C628.3070300@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Hi Tejun,
On Mon, 07 Sep 2009 17:36:56 +0900 Tejun Heo <tj@kernel•org> wrote:
>
> Stephen Rothwell wrote:
> >
> > I *think* the changes in the percpu tree supercede those in Linus' tree,
> > so I have used those.
>
> Yes, the changes in Linus's tree are backported from devel branch but
> the devel already has moved on and dropped one of the changes. I'll
> merge Linus's tree into percpu devel branch.
Thanks for the confirmation.
--
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-09-07 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 8:22 linux-next: manual merge of the percpu tree with Linus' tree Stephen Rothwell
2009-09-07 8:36 ` Tejun Heo
2009-09-07 10:24 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-30 8:20 Stephen Rothwell
2009-10-30 10:02 ` Tejun Heo
2009-10-31 4:23 ` Stephen Rothwell
2009-07-01 7:25 Stephen Rothwell
2009-07-01 7:19 Stephen Rothwell
2009-06-29 5:33 Stephen Rothwell
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=20090907202420.c0bd57e5.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cl@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=rusty@rustcorp$(echo .)com.au \
--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