From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro•org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Cc: Loic Poulain <loic.poulain@linaro•org>,
Network Development <netdev@vger•kernel.org>,
Matthew Wilcox <willy@infradead•org>,
Du Cheng <ducheng2@gmail•com>,
Bjorn Andersson <bjorn.andersson@linaro•org>
Subject: Re: [PATCH net-next] qrtr: move to staging
Date: Mon, 29 Mar 2021 16:37:41 +0530 [thread overview]
Message-ID: <20210329110741.GC2763@work> (raw)
In-Reply-To: <YGGz/BaibxykzxOW@kroah.com>
On Mon, Mar 29, 2021 at 01:03:24PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Mar 29, 2021 at 04:22:36PM +0530, Manivannan Sadhasivam wrote:
> > Hi Greg,
> >
> > On Mon, Mar 29, 2021 at 11:47:12AM +0200, Loic Poulain wrote:
> > > Hi Greg,
> > >
> > > On Sun, 28 Mar 2021 at 14:28, Greg Kroah-Hartman <gregkh@linuxfoundation•org>
> > > 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>
> > > >
> > >
> > > As far as I know, QRTR/IPCR is still commonly used with Qualcomm-based
> > > platforms for accessing various components of the SoC.
> > > CCing Bjorn and Mani, In case they are interested in taking maintenance of
> > > that.
> > >
> >
> > As Loic said, QRTR is an integral component used in various Qualcomm based
> > upstream supported products like ChromeOS, newer WLAN chipsets (QCA6390) etc...
> >
> > It is unfortunate that no one stepped up so far to maintain it. After
> > having an internal discussion, I decided to pitch in as a maintainer. I'll
> > send the MAINTAINERS change to netdev list now.
>
> Great, can you also fix up the reported problems with the codebase that
> resulted in this "ask for removal"?
>
Yes, ofc. I do see couple of Syzbot bug reports now... I will look into them.
It turned out I fixed one of them earlier but should've handled all :)
Thanks,
Mani
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-03-29 11:08 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
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 [this message]
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=20210329110741.GC2763@work \
--to=manivannan.sadhasivam@linaro$(echo .)org \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=ducheng2@gmail$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=loic.poulain@linaro$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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