From: Kalle Valo <kvalo@codeaurora.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Christian Lamparter <chunkeey@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-wireless@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intersil: remove obsolete prism54 wireless driver
Date: Wed, 28 Jul 2021 17:54:40 +0300 [thread overview]
Message-ID: <87pmv2fpzj.fsf@codeaurora.org> (raw)
In-Reply-To: <YP//NPZbVXZ5efZJ@bombadil.infradead.org> (Luis Chamberlain's message of "Tue, 27 Jul 2021 05:42:28 -0700")
Luis Chamberlain <mcgrof@kernel.org> writes:
> On Tue, Jul 27, 2021 at 09:07:48AM +0300, Kalle Valo wrote:
>> Christian Lamparter <chunkeey@gmail.com> writes:
>>
>> > On 16/07/2021 00:06, Luis Chamberlain wrote:
>> >> On Tue, Jul 13, 2021 at 07:40:25AM +0200, Lukas Bulwahn wrote:
>> >>> Commit 1d89cae1b47d ("MAINTAINERS: mark prism54 obsolete") indicated the
>> >>> prism54 driver as obsolete in July 2010.
>> >>>
>> >>> Now, after being exposed for ten years to refactoring, general tree-wide
>> >>> changes and various janitor clean-up, it is really time to delete the
>> >>> driver for good.
>> >>>
>> >>> This was discovered as part of a checkpatch evaluation, investigating all
>> >>> reports of checkpatch's WARNING:OBSOLETE check.
>> >>>
>> >>> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>> >>> ---
>> >
>> > noted. Farewell.
>>
>> How do we know that there are no users left? It's surprising how ancient
>> hardware some people use. Is the driver broken or what?
>>
>> (Reads commit 1d89cae1b47d)
>>
>> Ah, p54 is supposed to replace prism54. Does that include all the
>> hardware supported by prism54?
>
> There was a one off chipset someone told me about long ago that p54
> didn't work for. But that persond disappeared from the face of the
> earth. Additionally, distributions have been blacklisting prism54
> for years now.
>
>> If yes, that should be clearly documented
>> in the commit log and I can add that.
>
> Agreed. Feel free to quote the above.
Thanks, will do.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-07-28 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 5:40 [PATCH] intersil: remove obsolete prism54 wireless driver Lukas Bulwahn
2021-07-15 22:06 ` Luis Chamberlain
2021-07-16 7:25 ` Christian Lamparter
2021-07-27 6:07 ` Kalle Valo
2021-07-27 12:42 ` Luis Chamberlain
2021-07-28 14:54 ` Kalle Valo [this message]
2021-08-06 8:57 ` Kalle Valo
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=87pmv2fpzj.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=dwaipayanray1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).