From: Keir Fraser <keir@xensource.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: Jun Kamada <kama@jp.fujitsu.com>,
xen-devel@lists.xensource.com,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdefARCH_HAS_DEV_MEM" to archtecture specific file_operations.
Date: Fri, 13 Jul 2007 16:09:30 +0100 [thread overview]
Message-ID: <C2BD543A.126AB%keir@xensource.com> (raw)
In-Reply-To: <20070713145423.GA24654%yamahata@valinux.co.jp>
On 13/7/07 15:54, "Isaku Yamahata" <yamahata@valinux.co.jp> wrote:
> On Fri, Jul 13, 2007 at 01:54:10PM +0100, Keir Fraser wrote:
>>
>> I am happy to apply these if this is the right direction for ia64. Will
>> someone else (e.g., Alex, Isaku) ack them if so, please?
>
> Fine for me.
> acked-by: Isaku Yamahata <yamahata@valinux.co.jp>
Okay, revert of 12513 is now applied. I assume the other patch will be
applied to the ia64 linux tree.
-- Keir
prev parent reply other threads:[~2007-07-13 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707061715.l66HF2Ns030133@xenbits.xensource.com>
2007-07-06 20:25 ` [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations Hollis Blanchard
2007-07-07 9:01 ` Keir Fraser
2007-07-09 19:20 ` Hollis Blanchard
2007-07-09 19:26 ` Keir Fraser
2007-07-09 19:41 ` Hollis Blanchard
2007-07-09 20:23 ` [XenPPC] " Jimi Xenidis
2007-07-09 21:20 ` Jimi Xenidis
2007-07-11 5:44 ` Jun Kamada
2007-07-11 10:00 ` Keir Fraser
2007-07-12 11:05 ` Jun Kamada
2007-07-13 2:42 ` [Xen-devel] Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdefARCH_HAS_DEV_MEM" " Akio Takebe
2007-07-13 12:54 ` Keir Fraser
2007-07-13 14:54 ` Isaku Yamahata
2007-07-13 15:09 ` Keir Fraser [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=C2BD543A.126AB%keir@xensource.com \
--to=keir@xensource.com \
--cc=hollisb@us.ibm.com \
--cc=kama@jp.fujitsu.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.