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,
Micky Ching <micky_ching@realsil.com.cn>,
wwang <wei_wang@realsil.com.cn>,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Justin Stitt <justinstitt@google.com>,
Julia Lawall <julia.lawall@inria.fr>,
Soumya Negi <soumya.negi97@gmail.com>
Subject: Re: [RFC] staging: rts5208: Proposal to delete driver rts5208
Date: Wed, 9 Oct 2024 11:40:58 +0200 [thread overview]
Message-ID: <2024100943-shank-washed-a765@gregkh> (raw)
In-Reply-To: <b7b646d2-6987-4557-94c1-5fcd8d3d5ebc@gmail.com>
On Sun, Sep 29, 2024 at 02:37:16PM +0200, Philipp Hortmann wrote:
> Dear Sirs,
>
> Wei Wang from Realsil contributed this driver in 2011.
>
> The following points let me propose to delete the driver:
> - This driver generates maintenance workload
> - Did not find minimal documentation on the web.
> - No blog entries about anyone using the rts5208 and rts5288 during the last
> years.
> - Did not find any device that may has it in and is still available on the
> market: Dell Latitude 2120, Lenovo ThinkPad Edge 130, Lenovo x121e
>
> 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.
>
> Thanks for any response about your thoughts.
Again, no objection from me, please send a patch to delete it.
thanks,
greg k-h
prev parent reply other threads:[~2024-10-09 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 12:37 [RFC] staging: rts5208: Proposal to delete driver rts5208 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=2024100943-shank-washed-a765@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=julia.lawall@inria.fr \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=micky_ching@realsil.com.cn \
--cc=philipp.g.hortmann@gmail.com \
--cc=soumya.negi97@gmail.com \
--cc=wei_wang@realsil.com.cn \
--cc=yongjun_wei@trendmicro.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.