From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org,
"Philipp Hortmann" <philipp.g.hortmann@gmail.com>,
"Dominik Karol Piątkowski"
<dominik.karol.piatkowski@protonmail.com>
Subject: Re: [PATCH v6.12] staging: rtl8712: Remove driver using deprecated API wext
Date: Thu, 27 Nov 2025 20:02:10 +0100 [thread overview]
Message-ID: <2025112755-wince-upstage-372f@gregkh> (raw)
In-Reply-To: <20251127182037.2174177-1-linux@roeck-us.net>
On Thu, Nov 27, 2025 at 10:20:37AM -0800, Guenter Roeck wrote:
> From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
>
> commit e8785404de06a69d89dcdd1e9a0b6ea42dc6d327 upstream.
>
> This driver is in the staging area since 2010.
>
> The following reasons lead to the removal:
> - This driver generates maintenance workload for itself and for API wext
> - A MAC80211 driver was available in 2016 time frame; This driver does
> not compile anymore but would be a better starting point than the
> current driver. Here the note from the TODO file:
> A replacement for this driver with MAC80211 support is available
> at https://github.com/chunkeey/rtl8192su
> - no progress changing to mac80211
> - Using this hardware is security wise not state of the art as WPA3 is
> not supported.
>
> The longterm kernels will still support this hardware for years.
That's not going to be true :)
> Like this ?
I like it, removing code is always good. If we find people that are
relying on this, we can revisit it. I'll queue this up for the next
round of stable releases after these.
thanks!
greg k-h
prev parent reply other threads:[~2025-11-27 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 18:20 [PATCH v6.12] staging: rtl8712: Remove driver using deprecated API wext Guenter Roeck
2025-11-27 19:02 ` Greg Kroah-Hartman [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=2025112755-wince-upstage-372f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dominik.karol.piatkowski@protonmail.com \
--cc=linux@roeck-us.net \
--cc=philipp.g.hortmann@gmail.com \
--cc=stable@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