From: arun.ramamurthy@broadcom.com (Arun Ramamurthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/2] usb: ehci-platform: add support for multiple phys per controller
Date: Wed, 21 Jan 2015 11:13:06 -0800 [thread overview]
Message-ID: <54BFFA42.4010506@broadcom.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1501211002380.1670-100000@iolanthe.rowland.org>
Thanks Alan. I did run check patch and I had no errors or warnings.
I explained my changes in v3 in the cover patch, did that not come
through or is it convention to do it in the individual patch?
Is the ack for the ohci patch as well? Thanks
Arun Ramamurthy
On 15-01-21 07:03 AM, Alan Stern wrote:
> On Mon, 19 Jan 2015 arun.ramamurthy at broadcom.com wrote:
>
>> From: Arun Ramamurthy <arunrama@broadcom.com>
>>
>> Added support for cases where one controller is connected
>> to multiple phys.
>>
>> Signed-off-by: Arun Ramamurthy <arunrama@broadcom.com>
>> Reviewed-by: Ray Jui <rjui@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.com>
>> Tested-by: Scott Branden <sbranden@broadcom.com>
>> ---
>
> Right here is where you should explain how v3 of this patch is
> different from v2.
>
> Anyway, it looks good.
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> Did you run it through checkpatch.pl?
>
> Alan Stern
>
next prev parent reply other threads:[~2015-01-21 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 0:05 [PATCHv3 0/2] Added Multiple Phy support for ehci and ohci drivers arun.ramamurthy at broadcom.com
2015-01-20 0:05 ` [PATCHv3 1/2] usb: ehci-platform: add support for multiple phys per controller arun.ramamurthy at broadcom.com
2015-01-21 15:03 ` Alan Stern
2015-01-21 19:13 ` Arun Ramamurthy [this message]
2015-01-21 20:40 ` Alan Stern
2015-01-20 0:05 ` [PATCHv3 2/2] usb: ohci-platform: " arun.ramamurthy at broadcom.com
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=54BFFA42.4010506@broadcom.com \
--to=arun.ramamurthy@broadcom.com \
--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).