From: Axel Haslam <ahaslam@baylibre.com>
To: khilman@kernel.org, nsekhar@ti.com, david@lechnology.com,
gregkh@linuxfoundation.org, kishon@ti.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Axel Haslam <ahaslam@baylibre.com>
Subject: [PATCH v2 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx
Date: Thu, 3 Nov 2016 17:03:08 +0100 [thread overview]
Message-ID: <20161103160308.29588-4-ahaslam@baylibre.com> (raw)
In-Reply-To: <20161103160308.29588-1-ahaslam@baylibre.com>
The davinci ohci driver name (currently "ohci") is too generic.
To be consistent with other usb dirvers, append the "-da8xx" postfix
to the name.
Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
---
drivers/usb/host/ohci-da8xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/ohci-da8xx.c b/drivers/usb/host/ohci-da8xx.c
index 30c4878..429d58b 100644
--- a/drivers/usb/host/ohci-da8xx.c
+++ b/drivers/usb/host/ohci-da8xx.c
@@ -27,7 +27,7 @@
#include "ohci.h"
#define DRIVER_DESC "DA8XX"
-#define DRV_NAME "ohci"
+#define DRV_NAME "ohci-da8xx"
static struct hc_driver __read_mostly ohci_da8xx_hc_driver;
--
2.10.1
next prev parent reply other threads:[~2016-11-03 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 16:03 [PATCH v2 0/3] davinci: ohci: fix usb ohci device name Axel Haslam
2016-11-03 16:03 ` [PATCH v2 1/3] ARM: davinci: da8xx: Fix " Axel Haslam
2016-11-23 12:07 ` Sekhar Nori
2016-11-03 16:03 ` [PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx Axel Haslam
2016-11-05 5:21 ` Kishon Vijay Abraham I
2016-11-03 16:03 ` Axel Haslam [this message]
2016-11-21 17:10 ` [PATCH v2 3/3] usb: ohci-da8xx: rename driver " Axel Haslam
2016-11-23 9:32 ` Greg KH
2016-11-03 16:49 ` [PATCH v2 0/3] davinci: ohci: fix usb ohci device name David Lechner
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=20161103160308.29588-4-ahaslam@baylibre.com \
--to=ahaslam@baylibre.com \
--cc=david@lechnology.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nsekhar@ti.com \
/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
all inboxes | Powered by JetHome®