From: "Arnd Bergmann" <arnd@arndb.de>
To: "Philipp Hortmann" <philipp.g.hortmann@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Kalle Valo" <kvalo@kernel.org>
Subject: Re: [RFC] staging: wlan-ng: Driver broken since kernel 5.15
Date: Tue, 12 Mar 2024 16:57:38 +0100 [thread overview]
Message-ID: <35b27047-4e5f-4e22-ab7e-cd5ee983a232@app.fastmail.com> (raw)
In-Reply-To: <6dc14151-e71e-4118-826d-3ca5c8ee907f@gmail.com>
On Sat, Mar 9, 2024, at 23:09, Philipp Hortmann wrote:
> Hi,
>
> I would remove the driver from the mainline kernel. What are your thoughts?
>
> I bought two WLAN devices (DUT: D-Link DWL-122 and T-Sinus 111 data)
> that are supported by wlan-ng driver. Issue is that the driver is not
> working anymore.
I don't think it matters much either way. I did send the patches
to remove wlan drivers that were either using the old pcmcia
interfaces or the old wireless extensions that I think we should
try to eventually kill off entirely, but this driver uses neither
of them and as a result has a lower maintenance cost.
On the other hand, there is also little benefit in keeping the
driver if it's known to be broken, given how better USB wireless
adapters are dirt cheap and widely available. Even if we find and
fix all the bugs in this driver, any supported 802.11n device
would be better in practice.
Arnd
prev parent reply other threads:[~2024-03-12 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 22:09 [RFC] staging: wlan-ng: Driver broken since kernel 5.15 Philipp Hortmann
2024-03-11 7:04 ` Dan Carpenter
2024-03-17 20:07 ` Philipp Hortmann
2024-03-17 20:20 ` Arnd Bergmann
2024-03-18 8:01 ` Dan Carpenter
2024-03-18 8:30 ` Arnd Bergmann
2024-03-18 17:07 ` Philipp Hortmann
2024-03-12 15:57 ` Arnd Bergmann [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=35b27047-4e5f-4e22-ab7e-cd5ee983a232@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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