From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Stable Kernel <stable@kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [GIT PULL] Xen bugfixes
Date: Thu, 10 Sep 2009 12:02:32 -0700 [thread overview]
Message-ID: <4AA94D48.5010401@goop.org> (raw)
In-Reply-To: <20090910172629.GA10689@elte.hu>
On 09/10/09 10:26, Ingo Molnar wrote:
> Looks like a nice cleanup. Mind sticking it into your next pull
> request?
>
The following changes since commit 2496afbf1e50c70f80992656bcb730c8583ddac3:
Yang Xiaowei (1):
xen: use stronger barrier after unlocking lock
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git bugfix
Jeremy Fitzhardinge (1):
x86: split __phys_addr out into separate file
arch/x86/mm/Makefile | 4 +-
arch/x86/mm/ioremap.c | 72 +-----------------------------------------------
arch/x86/mm/physaddr.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++
arch/x86/mm/physaddr.h | 10 ++++++
4 files changed, 83 insertions(+), 73 deletions(-)
create mode 100644 arch/x86/mm/physaddr.c
create mode 100644 arch/x86/mm/physaddr.h
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Tejun Heo <tj@kernel.org>,
Stable Kernel <stable@kernel.org>
Subject: Re: [GIT PULL] Xen bugfixes
Date: Thu, 10 Sep 2009 12:02:32 -0700 [thread overview]
Message-ID: <4AA94D48.5010401@goop.org> (raw)
In-Reply-To: <20090910172629.GA10689@elte.hu>
On 09/10/09 10:26, Ingo Molnar wrote:
> Looks like a nice cleanup. Mind sticking it into your next pull
> request?
>
The following changes since commit 2496afbf1e50c70f80992656bcb730c8583ddac3:
Yang Xiaowei (1):
xen: use stronger barrier after unlocking lock
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git bugfix
Jeremy Fitzhardinge (1):
x86: split __phys_addr out into separate file
arch/x86/mm/Makefile | 4 +-
arch/x86/mm/ioremap.c | 72 +-----------------------------------------------
arch/x86/mm/physaddr.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++
arch/x86/mm/physaddr.h | 10 ++++++
4 files changed, 83 insertions(+), 73 deletions(-)
create mode 100644 arch/x86/mm/physaddr.c
create mode 100644 arch/x86/mm/physaddr.h
J
next prev parent reply other threads:[~2009-09-10 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:51 [GIT PULL] Xen bugfixes Jeremy Fitzhardinge
2009-09-09 23:51 ` Jeremy Fitzhardinge
2009-09-10 5:16 ` Ingo Molnar
2009-09-10 5:16 ` Ingo Molnar
2009-09-10 17:16 ` Jeremy Fitzhardinge
2009-09-10 17:16 ` Jeremy Fitzhardinge
2009-09-10 17:26 ` Ingo Molnar
2009-09-10 17:26 ` Ingo Molnar
2009-09-10 19:02 ` Jeremy Fitzhardinge [this message]
2009-09-10 19:02 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-12-03 23:46 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=4AA94D48.5010401@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=stable@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 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.