From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Sven Van Asbroeck <TheSven73@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: "Ricardo B. Marliere" <ricardo@marliere.net>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Ruan Jinjie" <ruanjinjie@huawei.com>,
"Zhu Wang" <wangzhu9@huawei.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Deepak R Varma" <drv@mailo.com>,
"Ajith P V" <ajithpv.linux@gmail.com>,
"Tian Tao" <tiantao6@hisilicon.com>,
"Rikard Falkeborn" <rikard.falkeborn@gmail.com>,
"Ding Xiang" <dingxiang@cmss.chinamobile.com>,
"Jing Xiangfeng" <jingxiangfeng@huawei.com>,
"Cristiane Naves" <cristianenavescardoso09@gmail.com>,
YueHaibing <yuehaibing@huawei.com>,
"Oscar Gomez Fuente" <oscargomezf@gmail.com>,
"Nicholas Mc Guire" <hofrat@osadl.org>
Subject: [RFC] staging: fieldbus: Proposal to delete driver
Date: Sat, 19 Oct 2024 08:45:37 +0200 [thread overview]
Message-ID: <96ae2b42-c0ce-4d9a-8933-eb874dc5589b@gmail.com> (raw)
Dear Sirs,
Sven Van Asbroeck contributed this driver in 2019.
The following points let me propose to delete the driver:
- This driver generates maintenance workload
- only 11 patches during the last 3 years. Part of the patches seem to
be motivated because of maintenance (for example - remove deprecated
function)
- Maintainer lost interest, last "Reviewed-by:" is May 2021
- no blog about usage of this driver
The staging subsystem is the way for drivers into the kernel - at
current speed and interest this is never going to happen.
I think that fieldbus is an interesting topic. But when almost nobody
cares about this driver, it does not make sense to keep it.
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. This time can
be shorted or extended by appropriate comments.
Bye Philipp
reply other threads:[~2024-10-19 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=96ae2b42-c0ce-4d9a-8933-eb874dc5589b@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=TheSven73@gmail.com \
--cc=ajithpv.linux@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=cristianenavescardoso09@gmail.com \
--cc=dingxiang@cmss.chinamobile.com \
--cc=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=hofrat@osadl.org \
--cc=jingxiangfeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=oscargomezf@gmail.com \
--cc=ricardo@marliere.net \
--cc=rikard.falkeborn@gmail.com \
--cc=ruanjinjie@huawei.com \
--cc=tiantao6@hisilicon.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wangzhu9@huawei.com \
--cc=yuehaibing@huawei.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