From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 7/7] Celleb: update for PCI
Date: Thu, 27 Sep 2007 18:25:27 +1000 [thread overview]
Message-ID: <1190881527.6158.6.camel@pasglop> (raw)
In-Reply-To: <200709261409.32231.arnd@arndb.de>
On Wed, 2007-09-26 at 14:09 +0200, Arnd Bergmann wrote:
> Is there a way that we can make that code common? I guess there could be a
> file in arch/powerpc/sysdev that can handle this correctly for all hardware
> that requires this particular workaround (currently celleb and QS20, but
> potentially more).
We could move it to something like sysdev/spider-pci-workarounds.c
Another thing to note is that the initial implementation I did for QS20
only does PCI, not PCIE. Maybe that's worth fixing on both.
Ben.
next prev parent reply other threads:[~2007-09-27 8:25 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 [this message]
2007-10-02 8:04 ` Ishizaki Kou
2007-10-02 8:18 ` Arnd Bergmann
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=1190881527.6158.6.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).