public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Tommaso Merciai" <tomm.merciai@gmail.com>,
	"Richard Meek" <osl2008@googlemail.com>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	"Xingquan Liu" <b1n@b1n.io>,
	"Dominik Karol Piątkowski"
	<dominik.karol.piatkowski@protonmail.com>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Pavan Bobba" <opensource206@gmail.com>,
	"Malcolm Priestley" <tvboxspy@gmail.com>,
	"Joe Perches" <joe@perches.com>
Subject: Re: [RFC] staging: vt6655: Proposal to delete driver vt6655_stage
Date: Wed, 9 Oct 2024 11:40:40 +0200	[thread overview]
Message-ID: <2024100923-player-directive-ffa8@gregkh> (raw)
In-Reply-To: <718c0476-c4bc-4a72-a1e4-483697c7eff2@gmail.com>

On Sun, Sep 29, 2024 at 10:09:02AM +0200, Philipp Hortmann wrote:
> 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 but this lasts only for a second. Typically
> throughput is 1.7MBytes/s.
> - Depending on the number of devices on the channel the device looses
> connection and cannot reconnect for 5-60 seconds. Watching a youtube video
> is OK because of the buffer. But surfing can then be really a pain.
> - Its form factor is mini PCI (not miniPCIe) that is really old and large.
> - Hardly not to buy. (https://www.ebay.com/sch/i.html?_from=R40&_trksid=p4432023.m570.l1313&_nkw=vnt6655&_sacat=0)
> only 70$ ;-) including shipment.
> 
> 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 for some dollars and
> play around which is fun.
> 
> Please consider that support will remain for years in the longterm kernels.

No objection from me, please send a patch deleting it and I will be glad
to take it.

thanks,

greg k-h

      reply	other threads:[~2024-10-09  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29  8:09 [RFC] staging: vt6655: Proposal to delete driver vt6655_stage Philipp Hortmann
2024-10-09  9:40 ` 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=2024100923-player-directive-ffa8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b1n@b1n.io \
    --cc=dan.carpenter@linaro.org \
    --cc=dominik.karol.piatkowski@protonmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=opensource206@gmail.com \
    --cc=osl2008@googlemail.com \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=tomm.merciai@gmail.com \
    --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