From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: mackerel: tidyup usbhs driver settings
Date: Wed, 15 Jun 2011 06:59:28 +0000 [thread overview]
Message-ID: <20110615065927.GO17891@linux-sh.org> (raw)
In-Reply-To: <w3p8vt362m4.wl%kuninori.morimoto.gx@renesas.com>
On Wed, Jun 15, 2011 at 03:58:13PM +0900, Magnus Damm wrote:
> On Wed, Jun 15, 2011 at 3:34 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> > On Wed, Jun 15, 2011 at 03:16:35PM +0900, Kuninori Morimoto wrote:
> >> - usb0 pipe is same as default. own pipe config is not needed
> >> - usb1 lost get_id function
> >>
> >> Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
> >
> > Looks good. Magnus, does this work for you?
>
> Yes, I tested the pipe portion of this patch yesterday. I trust that
> Morimoto-san got the get_id bit right.
>
> Acked-by: Magnus Damm <damm@opensource.se>
>
Good enough for me. Applied, thanks.
next prev parent reply other threads:[~2011-06-15 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 6:16 [PATCH] ARM: mach-shmobile: mackerel: tidyup usbhs driver settings Kuninori Morimoto
2011-06-15 6:34 ` Paul Mundt
2011-06-15 6:58 ` Magnus Damm
2011-06-15 6:59 ` Paul Mundt [this message]
2011-06-15 7:20 ` Paul Mundt
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=20110615065927.GO17891@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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