From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: shmobile: lager: USBHS callback elimination
Date: Sat, 12 Jul 2014 15:37:34 +0200 [thread overview]
Message-ID: <20140712133734.GA23843@verge.net.au> (raw)
In-Reply-To: <20140711162348.GF22572@saruman.home>
On Fri, Jul 11, 2014 at 11:23:48AM -0500, Felipe Balbi wrote:
> On Fri, Jul 11, 2014 at 05:41:52PM +0200, Simon Horman wrote:
> > On Fri, Jul 11, 2014 at 10:12:37AM -0500, Felipe Balbi wrote:
> > > On Fri, Jul 11, 2014 at 11:00:07AM +0200, Simon Horman wrote:
> > > > [Cc Felipe Balbi]
> > > >
> > > > On Thu, Jul 10, 2014 at 01:20:34AM -0700, Kuninori Morimoto wrote:
> > > > >
> > > > > Hi
> > > > >
> > > > > > Changes in v2:
> > > > > > - move phy handle to struct usbhs_priv
> > > > > > - add new default pipe type to driver
> > > > > > - remove pipe type from Lager board code
> > > > > >
> > > > > > Ulrich Hecht (2):
> > > > > > usb: renesas_usbhs: add R-Car Gen. 2 init and power control
> > > > > > ARM: shmobile: lager: remove USBHS callbacks
> > > > > >
> > > > > > arch/arm/mach-shmobile/board-lager.c | 126 ++++-------------------------------
> > > > > > drivers/usb/renesas_usbhs/Makefile | 2 +-
> > > > > > drivers/usb/renesas_usbhs/common.c | 66 ++++++++++++++++--
> > > > > > drivers/usb/renesas_usbhs/common.h | 2 +
> > > > > > drivers/usb/renesas_usbhs/rcar2.c | 76 +++++++++++++++++++++
> > > > > > drivers/usb/renesas_usbhs/rcar2.h | 4 ++
> > > > > > include/linux/usb/renesas_usbhs.h | 6 ++
> > > > > > 7 files changed, 163 insertions(+), 119 deletions(-)
> > > > > > create mode 100644 drivers/usb/renesas_usbhs/rcar2.c
> > > > > > create mode 100644 drivers/usb/renesas_usbhs/rcar2.h
> > > > >
> > > > > For all patches
> > > > >
> > > > > Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > > >
> > > > [snip]
> > > >
> > > > > I tested these patches on Lager legacy, and these patches worked correctly.
> > > > >
> > > > > Tested-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> > > >
> > > > Hi,
> > > >
> > > > it seems that the 2nd patch should go through my renesas tree
> > > > but it depends on the first patch which should be taken by
> > > > Felipe Balbi (Cced).
> > > >
> > > > Felipe, is there any chance that you could take this for v3.16?
> > > > I am quite happy to make a branch for you to pull for renesas_usbhs
> > > > if this would make your life easier.
> > >
> > > you need to take both patches or just patch 1 ?
> >
> > Please just take patch 1.
>
> will do.
Thanks.
Ulrich, please repost patch #2 once patch #1 hits an rc release.
next prev parent reply other threads:[~2014-07-12 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 7:53 [PATCH v2 0/2] ARM: shmobile: lager: USBHS callback elimination Ulrich Hecht
2014-07-10 7:53 ` [PATCH v2 1/2] usb: renesas_usbhs: add R-Car Gen. 2 init and power control Ulrich Hecht
2014-07-10 7:54 ` [PATCH v2 2/2] ARM: shmobile: lager: remove USBHS callbacks Ulrich Hecht
2014-07-10 8:20 ` [PATCH v2 0/2] ARM: shmobile: lager: USBHS callback elimination Kuninori Morimoto
2014-07-11 9:00 ` Simon Horman
2014-07-11 15:12 ` Felipe Balbi
2014-07-11 15:41 ` Simon Horman
2014-07-11 16:23 ` Felipe Balbi
2014-07-12 13:37 ` Simon Horman [this message]
2014-07-11 0:54 ` Yoshihiro Shimoda
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=20140712133734.GA23843@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).