From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/3] xen: setup percpu data pointers
Date: Thu, 5 Feb 2009 15:57:41 +0100 [thread overview]
Message-ID: <20090205145741.GC23903@elte.hu> (raw)
In-Reply-To: <498ABFA9.7060203@kernel.org>
* Tejun Heo <tj@kernel.org> wrote:
> Jeremy Fitzhardinge wrote:
> > Tejun Heo wrote:
> >> Tejun Heo wrote:
> >>
> >>> Applied 1-3 to #tj-percpu with trivial modification on #2 (will reply
> >>> to the message).
> >>>
> >>
> >> Oh... hpa already merged them into x86/paravirt. I'll just pull
> >> x86/paravirt into core/percpu because the first patch needs to be in
> >> core/percpu to keep xen working.
> >>
> >> hpa, can you please take the other xen patch[1] into x86/paravirt too?
> >> So that I can receive it via you?
> >
> > Looks like its already there.
>
> Yes, right, which means tj-percpu == x86/paravirt for the time being.
> Ingo, please pull from the following to fast forward core/percpu to
> x86/paravirt (or you can just do it yourself :-)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
done, thanks Tejun. Testing results look good so far.
Ingo
next prev parent reply other threads:[~2009-02-05 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:55 [PATCH 1/3] xen: setup percpu data pointers Jeremy Fitzhardinge
2009-02-05 6:29 ` Tejun Heo
2009-02-05 6:49 ` Tejun Heo
2009-02-05 7:17 ` Jeremy Fitzhardinge
2009-02-05 10:30 ` Tejun Heo
2009-02-05 14:57 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-31 1:42 Jeremy Fitzhardinge
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=20090205145741.GC23903@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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