Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: david@lechnology.com (David Lechner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: davinci: da8xx: Fix ohci driver name
Date: Wed, 2 Nov 2016 16:38:24 -0500	[thread overview]
Message-ID: <e819cbfc-e2e6-ccc0-1178-cfe5a85098a8@lechnology.com> (raw)
In-Reply-To: <20161102124435.31777-2-ahaslam@baylibre.com>

On 11/02/2016 07:44 AM, Axel Haslam wrote:
> There is a single instance of the ohci driver,
> while the clk lookup table is making reference to "ohci"
> other subsystems (such as phy) are looking for "ohci.0"
>

This patch changes the "device" name, not the "driver" name. You use 
"driver" above and in the subject.

> Since there is a single ohci instance, change the dev id
> to -1, and add the "-da8xx" for consitancy with the musb
> driver name.

It would be more accurate to say that you are adding "-da8xx" because 
you are also changing the ohci _driver_ name in a separate patch.

>
> Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
> ---

  reply	other threads:[~2016-11-02 21:38 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 [this message]
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
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=e819cbfc-e2e6-ccc0-1178-cfe5a85098a8@lechnology.com \
    --to=david@lechnology.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