From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: "Malcolm Priestley" <tvboxspy@gmail.com>,
"Teddy Engel" <engel.teddy@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Straube" <straube.linux@gmail.com>,
"Sathish Kumar" <skumark1902@gmail.com>,
"Florian Ziegler" <florian.ziegler@posteo.de>,
"Pritthijit Nath" <pritthijit.nath@icloud.com>,
"Arnd Bergmann" <arnd@arndb.de>,
tdavies@darkphysics.net, m.omerfarukbulut@gmail.com,
"Dominik Karol Piątkowski"
<dominik.karol.piatkowski@protonmail.com>
Subject: [RFC] staging: vt6656: Proposal to delete driver vt6656_stage
Date: Fri, 11 Oct 2024 20:59:44 +0200 [thread overview]
Message-ID: <d7ef2954-21d0-4ddc-85d3-1334e7270ced@gmail.com> (raw)
Dear Sirs,
Forest Bond contributed this driver in 2009.
The following points let me propose to delete the driver:
- This driver generates maintenance workload
- This driver has a maximum 54MBit/s as it supports only 802.11 b/g.
Peak throughput is 3MBytes/s.
- ping times can be 17ms are often above 500ms and worst case 22 seconds.
I suggest deleting the driver as it no longer meets current expectations.
Former Maintainer Forest Bond <forest@alittletooquiet.net> is unreachable.
The staging subsystem needs to focus on drivers that support usable
hardware that is available. Newbies can then get the hardware and play
around which is fun.
Please consider that support will remain for years in the longterm kernels.
Thanks for any response about your thoughts.
No response will result in a patch for removal in 14 days.
Bye Philipp
next reply other threads:[~2024-10-11 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 18:59 Philipp Hortmann [this message]
2024-10-12 8:00 ` [RFC] staging: vt6656: Proposal to delete driver vt6656_stage Greg Kroah-Hartman
2024-10-12 9:02 ` Malcolm Priestley
2024-10-12 10:04 ` Malcolm Priestley
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=d7ef2954-21d0-4ddc-85d3-1334e7270ced@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=arnd@arndb.de \
--cc=dominik.karol.piatkowski@protonmail.com \
--cc=engel.teddy@gmail.com \
--cc=florian.ziegler@posteo.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=m.omerfarukbulut@gmail.com \
--cc=pritthijit.nath@icloud.com \
--cc=skumark1902@gmail.com \
--cc=straube.linux@gmail.com \
--cc=tdavies@darkphysics.net \
--cc=tvboxspy@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