From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rusty Russell <rusty@rustcorp.com.au>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
cpw@sgi.com
Subject: Re: #tj-percpu has been rebased
Date: Sat, 31 Jan 2009 14:28:28 +0100 [thread overview]
Message-ID: <20090131132828.GA17271@elte.hu> (raw)
In-Reply-To: <4983E5D3.3040100@kernel.org>
* Tejun Heo <tj@kernel.org> wrote:
> Hello, again.
>
> Please disregard the previous two rebased trees. There has been a
> major communication misunderstanding between Ingo and me leading to
> the rebased branches. Here is yet another, hopefully final, merged
> tree which builds on top of tip/core/percpu and took only about ten
> minutes as opposed to hours. :-)
>
> * Three xen fix related patches merged. Later threes conflicted in
> non-minor way. Requested refresh.
>
> * Cliff Wickman's UV flush fix patch revived and merged.
>
> * Pull in linus#master[1].
>
> Anyways, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
>
> The commit ID should be da2c0b021cde94866f1e492f940aad29e8f61258.
>
> Sorry about the mess but this one should be the safe one to post
> patches against.
Very nice - pulled into tip/core/percpu, thanks Tejun!
Ingo
next prev parent reply other threads:[~2009-01-31 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 17:05 #tj-percpu has been rebased Tejun Heo
2009-01-31 5:46 ` Tejun Heo
2009-01-31 13:28 ` Ingo Molnar [this message]
2009-02-02 9:04 ` Rusty Russell
2009-02-04 3:18 ` Tejun Heo
2009-02-12 3:37 ` Tejun Heo
2009-02-12 3:44 ` Tejun Heo
2009-02-13 20:58 ` Rusty Russell
2009-02-13 21:17 ` Jeremy Fitzhardinge
2009-02-13 22:59 ` H. Peter Anvin
2009-02-14 0:45 ` Tejun Heo
2009-02-14 1:53 ` H. Peter Anvin
2009-02-14 2:10 ` Tejun Heo
2009-02-16 7:23 ` Rusty Russell
2009-02-16 17:28 ` H. Peter Anvin
2009-02-16 23:22 ` Rusty Russell
2009-02-16 23:28 ` H. Peter Anvin
2009-02-18 4:25 ` Rusty Russell
2009-02-18 6:40 ` H. Peter Anvin
2009-02-18 7:11 ` Rusty Russell
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=20090131132828.GA17271@elte.hu \
--to=mingo@elte.hu \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.