netdev - Re: [PATCH net-next] qrtr: move to staging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YGGz/BaibxykzxOW@kroah.com>
Date:   Mon, 29 Mar 2021 13:03:24 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     Loic Poulain <loic.poulain@...aro.org>,
        Network Development <netdev@...r.kernel.org>,
        Matthew Wilcox <willy@...radead.org>,
        Du Cheng <ducheng2@...il.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH net-next] qrtr: move to staging

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@...uxfoundation.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@...radead.org>
> > > Cc: Du Cheng <ducheng2@...il.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.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"?

thanks,

greg k-h