linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linuxppc-dev@ozlabs.org, Alistair Popple <alistair@popple.id.au>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH 4/8] IBM Akebono: Add support to the OHCI platform driver for PPC476GTR
Date: Fri, 10 Jan 2014 16:52:56 -0800	[thread overview]
Message-ID: <20140111005256.GB29302@kroah.com> (raw)
In-Reply-To: <52D09E19.9030302@cogentembedded.com>

On Sat, Jan 11, 2014 at 04:27:53AM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 11/22/2013 05:08 AM, Alistair Popple wrote:
> 
> >The IBM Akebono board uses the PPC476GTR SoC which has a OHCI
> >compliant USB host interface. This patch adds support for it to the
> >OHCI platform driver.
> 
> >As we use device tree to pass platform specific data instead of
> >platform data we remove the check for platform data and instead
> >provide reasonable defaults if no platform data is present. This is
> >similar to what is currently done in ehci-platform.c.
> >
> >Signed-off-by: Alistair Popple <alistair@popple.id.au>
> >Acked-by: Alan Stern <stern@rowland.harvard.edu>
> >Cc: linux-usb@vger.kernel.org
> 
>    Greg, why this patch hasn't been merged? Because it wasn't addressed to
> you (but BenH)? The other, ehci-platform.c patch didn't even get posted to
> linux-usb that time, but this one?

Probably, yes, if it's not sent to me, I'm guessing that the person
doesn't want it applied by me, especially if it's written by someone who
knows what they are doing.

I thought this was going through the PPC tree.  My USB patch queue is
empty, and closed, for 3.14-rc1.

thanks,

greg k-h

  reply	other threads:[~2014-01-11  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  2:07 [PATCH 0/8] IBM Akebono/PPC476GTR Support Alistair Popple
2013-11-22  2:08 ` [PATCH 1/8] IBM Akebono: Add support to AHCI platform driver Alistair Popple
2013-11-22 22:24   ` Tejun Heo
2013-11-22  2:08 ` [PATCH 2/8] IBM Akebono: Add a SDHCI " Alistair Popple
2013-12-17  1:11   ` Alistair Popple
2013-11-22  2:08 ` [PATCH 3/8] IBM Akebono: Add support for a new PHY interface to the IBM emac driver Alistair Popple
2013-12-05  4:49   ` Benjamin Herrenschmidt
2013-11-22  2:08 ` [PATCH 4/8] IBM Akebono: Add support to the OHCI platform driver for PPC476GTR Alistair Popple
2014-01-11  1:27   ` Sergei Shtylyov
2014-01-11  0:52     ` Greg KH [this message]
2014-01-11  1:06       ` Benjamin Herrenschmidt
2014-01-12 23:54         ` Alistair Popple
2013-11-22  2:08 ` [PATCH 5/8] ECHI Platform: Merge ppc-of EHCI driver into the ehci-platform driver Alistair Popple
2013-11-22  2:08 ` [PATCH 6/8] IBM Currituck: Clean up board specific code before adding Akebono code Alistair Popple
2013-11-22  2:08 ` [PATCH 7/8] IBM Akebono: Add the Akebono platform Alistair Popple
2013-11-22  2:08 ` [PATCH 8/8] powerpc: Added PCI MSI support using the HSTA module Alistair Popple

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=20140111005256.GB29302@kroah.com \
    --to=greg@kroah.com \
    --cc=alistair@popple.id.au \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sergei.shtylyov@cogentembedded.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 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).