Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx
Date: Fri, 4 Nov 2016 11:04:17 +0530	[thread overview]
Message-ID: <2c3b66c5-b148-252e-36a0-e067bb60191e@ti.com> (raw)
In-Reply-To: <fd6b848d-9740-70ef-6850-7f6a64e66bfb@ti.com>

Hi Kishon,

On Thursday 03 November 2016 10:20 PM, Kishon Vijay Abraham I wrote:
> 
> 
> On Wednesday 02 November 2016 06:14 PM, Axel Haslam wrote:
>> There is only one ohci on the da8xx series of chips,
>> so remove the ".0" when creating the phy. Also add
>> the "-da8xx" postfix to be consistent across davinci
>> usb drivers.
>>
>> Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
> 
> Acked-by: Kishon Vijay Abraham I <kishon@ti.com>

You will have to carry this patch from your tree. I thought I can carry
the entire series, but the USB patch depends on other patches that Greg
has already queued. So I think its best if the individual patches go
through their respective trees.

Note that there is a v2 already submitted.

Thanks,
Sekhar

  reply	other threads:[~2016-11-04  5:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 12:44 [PATCH 0/3] fix ohci phy name Axel Haslam
2016-11-02 12:44 ` [PATCH 1/3] ARM: davinci: da8xx: Fix ohci driver name Axel Haslam
2016-11-02 21:38   ` David Lechner
2016-11-02 12:44 ` [PATCH 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx Axel Haslam
2016-11-02 21:41   ` David Lechner
2016-11-03 16:50   ` Kishon Vijay Abraham I
2016-11-04  5:34     ` Sekhar Nori [this message]
2016-11-04 21:04       ` Kishon Vijay Abraham I
2016-11-02 12:44 ` [PATCH 3/3] usb: ohci-da8xx: rename driver " Axel Haslam
2016-11-02 21:44   ` David Lechner
2016-11-03 11:56   ` Sekhar Nori
2016-11-03 12:19     ` Axel Haslam
2016-11-03  8:24 ` [PATCH 0/3] fix ohci phy name Axel Haslam
2016-11-03 12:00   ` Sekhar Nori
2016-11-03 13:58     ` Axel Haslam

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=2c3b66c5-b148-252e-36a0-e067bb60191e@ti.com \
    --to=nsekhar@ti.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