From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] x86 updates for v2.6.30, final bits
Date: Sun, 29 Mar 2009 23:23:27 -0700 [thread overview]
Message-ID: <49D0655F.8080100@goop.org> (raw)
In-Reply-To: <20090328220307.GA16314@elte.hu>
Ingo Molnar wrote:
> Linus,
>
> Please pull the latest x86-stage-3-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-stage-3-for-linus
>
> This concludes the x86 merge window.
>
I'm planning on getting Xen changes into this merge window. I was
expecting you to at least take the branches which have an impact on the
arch/x86 side, but I guess there was a miscommunication there.
However, since all your pending x86 changes are now sent, do you have
any objections me sending out pull requests for the Xen changes I've
previously posted? If not, I'll start tomorrow.
Thanks,
J
prev parent reply other threads:[~2009-03-30 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 22:03 [git pull] x86 updates for v2.6.30, final bits Ingo Molnar
2009-03-29 0:15 ` Linus Torvalds
2009-03-29 1:19 ` Ingo Molnar
2009-03-30 6:23 ` Jeremy Fitzhardinge [this message]
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=49D0655F.8080100@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox