From: Arnd Bergmann <arnd@arndb•de>
To: Ishizaki Kou <kou.ishizaki@toshiba•co.jp>
Cc: linuxppc-dev@ozlabs•org, paulus@samba•org
Subject: Re: [PATCH 7/7] Celleb: update for PCI
Date: Tue, 2 Oct 2007 10:18:47 +0200 [thread overview]
Message-ID: <200710021018.48329.arnd@arndb.de> (raw)
In-Reply-To: <20071002.170439.-1300534196.kouish@swc.toshiba.co.jp>
On Tuesday 02 October 2007, Ishizaki Kou wrote:
> Though I agree it's better to make code common, I hope to keep them
> separate for now. Because I'm now developing PCI Express support and
> it also uses io-workaround mechanism. I'll try to make them common in
> this work.
Ok, fair enough. Let's use your current version for 2.6.24 and then
work on a new version that handles both PCI and PCIe correctly
on both platforms. I'm certainly interested in getting the PCIe
workarounds running on QS20 as well.
Arnd <><
prev parent reply other threads:[~2007-10-02 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 4:40 [PATCH 7/7] Celleb: update for PCI Ishizaki Kou
2007-09-26 12:09 ` Arnd Bergmann
2007-09-27 8:25 ` Benjamin Herrenschmidt
2007-10-02 8:04 ` Ishizaki Kou
2007-10-02 8:18 ` Arnd Bergmann [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=200710021018.48329.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=kou.ishizaki@toshiba$(echo .)co.jp \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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