From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Brownell <david-b@pacbell.net>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
linux-usb-devel@lists.sourceforge.net,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver
Date: Tue, 23 Oct 2007 10:37:00 -0500 [thread overview]
Message-ID: <20071023103700.595e9abd@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <200710101030.02349.sr@denx.de>
On Wed, 10 Oct 2007 10:30:02 +0200
Stefan Roese <sr@denx.de> wrote:
> On Wednesday 10 October 2007, Arnd Bergmann wrote:
> > > Do PPC folk sign off on how this is done?
> > >
> > > I don't follow all the ins/outs of the OF devtree stuff...
> >
> > The driver looks good to me, both the interaction with the of_platform_bus
> > layer and the handling of I/O addresses. I haven't actually tried running
> > it, but I'm rather confident that if it works on the Sequoia, it should
> > also do the right thing on any other powerpc system that has an EHCI on
> > some other (non-PCI) bus.
> >
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> Acked-by: Stefan Roese <sr@denx.de>
David, were you going to pull in the echi-ppc-of driver (patch 1 of
this series) for 2.6.24? Just trying to figure out if I need to pull
the other two patches into my tree.
josh
prev parent reply other threads:[~2007-10-23 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:25 [PATCH 0/3] usb: ehci ppc device-tree-aware driver Valentine Barshak
2007-09-24 19:26 ` [PATCH 1/3] usb: add device-tree-aware ehci driver Valentine Barshak
2007-09-24 19:27 ` [PATCH 2/3] usb: ehci-ppc-of dts bindings Valentine Barshak
2007-09-24 19:29 ` [PATCH 3/3] Add PowerPC 440EPx Sequoia ehci dts entry Valentine Barshak
2007-10-10 6:27 ` [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver David Brownell
2007-10-10 8:15 ` Arnd Bergmann
2007-10-10 8:30 ` Stefan Roese
2007-10-23 15:37 ` Josh Boyer [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=20071023103700.595e9abd@weaponx.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=david-b@pacbell.net \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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).