From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: netdev@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
Du Cheng <ducheng2@gmail.com>
Subject: Re: [PATCH net-next] qrtr: move to staging
Date: Mon, 29 Mar 2021 07:30:08 +0200 [thread overview]
Message-ID: <YGFl4IcdLfbsyO51@kroah.com> (raw)
In-Reply-To: <YGFi0uIfavNsXhfs@unreal>
On Mon, Mar 29, 2021 at 08:17:06AM +0300, Leon Romanovsky wrote:
> On Sun, Mar 28, 2021 at 02:26:21PM +0200, Greg Kroah-Hartman wrote:
> > There does not seem to be any developers willing to maintain the
> > net/qrtr/ code, so move it to drivers/staging/ so that it can be removed
> > from the kernel tree entirely in a few kernel releases if no one steps
> > up to maintain it.
> >
> > Reported-by: Matthew Wilcox <willy@infradead.org>
> > Cc: Du Cheng <ducheng2@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
>
> Greg,
>
> Why don't you simply delete it like other code that is not maintained?
"normally" we have been giving code a chance by having it live in
drivers/staging/ for a bit before removing it to allow anyone that
actually cares about the codebase to notice it before removing it.
We've done this for many drivers and code-chunks over the years, wimax
was one recent example.
Just trying to be nice :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-29 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 12:26 [PATCH net-next] qrtr: move to staging Greg Kroah-Hartman
2021-03-29 5:17 ` Leon Romanovsky
2021-03-29 5:30 ` Greg Kroah-Hartman [this message]
2021-03-29 6:30 ` Leon Romanovsky
2021-03-29 6:41 ` Greg Kroah-Hartman
[not found] ` <CAMZdPi_3B9Bxg=7MudFq+RnhD10Mm5QbX_pBb5vyPsZAC_bNOQ@mail.gmail.com>
2021-03-29 10:52 ` Manivannan Sadhasivam
2021-03-29 11:03 ` Greg Kroah-Hartman
2021-03-29 11:07 ` Manivannan Sadhasivam
2021-03-29 11:30 ` Matthew Wilcox
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=YGFl4IcdLfbsyO51@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ducheng2@gmail.com \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willy@infradead.org \
/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.