From: Frank Wunderlich <frank-w@public-files.de>
To: linux-mediatek@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Frank Wunderlich <linux@fw-web.de>, Bin Liu <b-liu@ti.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
David Miller <davem@davemloft.net>,
DENG Qingfang <dqfext@gmail.com>
Subject: Re: Re: [PATCH] musb: mediatek: rename driver
Date: Fri, 30 Apr 2021 16:38:03 +0200 [thread overview]
Message-ID: <16ABF577-4EE1-4BB3-A801-A4498CBFCFCE@public-files.de> (raw)
In-Reply-To: <YIwMvUVmeeYT1aph@kroah.com>
Am 30. April 2021 15:57:17 MESZ schrieb Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>Why not just have any new driver not use this name, as it is, it's not
>hurting anything.
I just want to make it clean for users/admins for what kind of device this module is for (vendor.ko is imho not good at least for vendors manufacturing such different devices).
And avoid such conflicts like the phy (which had reintroduced the unclear module name).
The new module will be renamed in next version..there is only discussion about the new name...and so i tried to fix the "other end".
>Until you can guarantee that renaming this is not
>going to break anything, I can not take it.
If a user/administrator installs a new major kernel version he needs to check if all is still working. Then the new module can be loaded...i don't see a real breakage or much work for "fix" this,but it's ok if you do not take it up.
This driver is afair available since 5.4 so i guess not much spreading in large productive environments mostly still using 4.14 or 4.4
I can repost with better description,but this is not needed if change itself will be rejected. So maybe anyone else can comment too.
regards Frank
prev parent reply other threads:[~2021-04-30 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 12:43 [PATCH] musb: mediatek: rename driver Frank Wunderlich
2021-04-30 12:54 ` Greg Kroah-Hartman
2021-04-30 13:30 ` Aw: " Frank Wunderlich
2021-04-30 13:57 ` Greg Kroah-Hartman
2021-04-30 14:38 ` Frank Wunderlich [this message]
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=16ABF577-4EE1-4BB3-A801-A4498CBFCFCE@public-files.de \
--to=frank-w@public-files.de \
--cc=b-liu@ti.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.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;
as well as URLs for NNTP newsgroup(s).