From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kalle Valo <kvalo@adurom.com>, Andrea Merello <andrea.merello@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
bernhard@schiffner-limbach.de, dan.carpenter@oracle.com
Subject: Re: [PATCH 1/4] rtl8180: change module name in rtl818Xpci
Date: Sat, 05 Apr 2014 01:23:21 -0500 [thread overview]
Message-ID: <533FA159.4030300@lwfinger.net> (raw)
In-Reply-To: <87bnwgif9n.fsf@purkki.adurom.net>
On 04/04/2014 11:14 PM, Kalle Valo wrote:
> Andrea Merello <andrea.merello@gmail.com> writes:
>
>> From: Larry Finger <Larry.Finger@lwfinger.net>
>>
>> rtl8180 driver can handle also rtl8185 and rtl8187SE cards,
>> however in userspace tools (network manager) it still appares
>> as "rtl8180".
>> This might lead the user to think the wrong driver is in use.
>>
>> This patch changes module name to "rtl818Xpci" that should be
>> more explanatory.
>>
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> Signed-off-by: Andrea Merello <andrea.merello@gmail.com>
>
> [...]
>
>> -obj-$(CONFIG_RTL8180) += rtl8180.o
>> +obj-$(CONFIG_RTL8180) += rtl818Xpci.o
>
> Aren't module names usually all lower case?
I do not feel strongly about this, but when I viewed the driver name in the KDE
applet for NetworkManager, the lower-case x sort of got lost, whereas the
upper-case one stood out. That was the reason for the way I wrote the patch the
way I did. In a terminal, the lc value looks OK. Perhaps I should have made it
rtl818x_pci.
Larry
next prev parent reply other threads:[~2014-04-05 6:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 16:15 [PATCH 1/4] rtl8180: change module name in rtl818Xpci Andrea Merello
2014-04-05 4:14 ` Kalle Valo
2014-04-05 6:23 ` Larry Finger [this message]
2014-04-05 6:39 ` Kalle Valo
2014-04-08 18:25 ` [PATCH v2 1/4] rtl8180: change module name in rtl818x_pci Andrea Merello
2014-04-09 16:10 ` John W. Linville
2014-04-09 16:30 ` Andrea Merello
2014-04-09 16:42 ` John W. Linville
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=533FA159.4030300@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=andrea.merello@gmail.com \
--cc=bernhard@schiffner-limbach.de \
--cc=dan.carpenter@oracle.com \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.