public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Priestley <tvboxspy@gmail.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: "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: Re: [RFC] staging: vt6656: Proposal to delete driver vt6656_stage
Date: Sat, 12 Oct 2024 11:04:33 +0100	[thread overview]
Message-ID: <d18e714d-787f-4d30-a32f-4b0f55d2f5be@gmail.com> (raw)
In-Reply-To: <b2ac0a21-989b-4f36-9bb4-923221a77fb1@gmail.com>

> 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. 


Hmm I see the rtl8192e driver has also gone need to buy another device.

Looks like staging is closing down sale.

Yeah okay from me to delete vt6656_stage it will be stable for a few years.

Regards
 

Malcolm




      reply	other threads:[~2024-10-12 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 18:59 [RFC] staging: vt6656: Proposal to delete driver vt6656_stage Philipp Hortmann
2024-10-12  8:00 ` Greg Kroah-Hartman
2024-10-12  9:02 ` Malcolm Priestley
2024-10-12 10:04   ` Malcolm Priestley [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=d18e714d-787f-4d30-a32f-4b0f55d2f5be@gmail.com \
    --to=tvboxspy@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=philipp.g.hortmann@gmail.com \
    --cc=pritthijit.nath@icloud.com \
    --cc=skumark1902@gmail.com \
    --cc=straube.linux@gmail.com \
    --cc=tdavies@darkphysics.net \
    /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