linux-kernel - RE: [EXT] Re: [PATCH v4 0/1] Patch History

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]

Date:   Fri, 15 Sep 2023 14:19:51 +0000
From:   David Lin <yu-hao.lin@....com>
To:     Brian Norris <briannorris@...omium.org>
CC:     "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Sharvari Harisangam <sharvari.harisangam@....com>,
        Pete Hsieh <tsung-hsien.hsieh@....com>,
        "kvalo@...nel.org" <kvalo@...nel.org>,
        "amitkarwar@...il.com" <amitkarwar@...il.com>,
        "ganapathi017@...il.com" <ganapathi017@...il.com>,
        "huxinming820@...il.com" <huxinming820@...il.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        Francesco Dolcini <francesco@...cini.it>
Subject: RE: [EXT] Re: [PATCH v4 0/1] Patch History

> From: Brian Norris <briannorris@...omium.org>
> Sent: Friday, September 15, 2023 9:29 AM
> To: David Lin <yu-hao.lin@....com>
> Cc: linux-wireless@...r.kernel.org; linux-kernel@...r.kernel.org; Sharvari
> Harisangam <sharvari.harisangam@....com>; Pete Hsieh
> <tsung-hsien.hsieh@....com>; kvalo@...nel.org; amitkarwar@...il.com;
> ganapathi017@...il.com; huxinming820@...il.com;
> davem@...emloft.net; edumazet@...gle.com; pabeni@...hat.com;
> Francesco Dolcini <francesco@...cini.it>
> Subject: [EXT] Re: [PATCH v4 0/1] Patch History
> 
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, report the message using the 'Report
> this email' button
> 
> 
> On Wed, Sep 13, 2023 at 11:42 PM David Lin <yu-hao.lin@....com> wrote:
> >
> > Hi Kalle,
> >
> >         Patch v4
> (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatch
> work.kernel.org%2Fproject%2Flinux-wireless%2Fpatch%2FPA4PR04MB963838
> F12BADC1B9FD377CB7D114A%40PA4PR04MB9638.eurprd04.prod.outlook.co
> m%2F&data=05%7C01%7Cyu-hao.lin%40nxp.com%7C75430d6f96b24d35e2e3
> 08dbb58b1ce5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6383
> 03381314463578%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd
> ata=RqbGAO0rATokTQI76roRAPl3Dr6OQKrhvesU%2FG6cEBU%3D&reserved=0)
> for host mlme had been submitted for a while.
> >
> >         Current state of this patch is "Deferred". I wonder when can this
> patch be reviewed and merged.
> >
> >         Is there anything I can do to speed up the acceptance of this
> patch by upstream?
> 
> You still haven't sent this to the correct maintainers (i.e., me) for one. I also
> thought there were outstanding unaddressed comments from Francesco.
> And given how much Francesco looked, I'd appreciate getting his
> Reviewed-by when he's actually happy with it.

I think I already replied Francesco's feedbacks. For example, patch history and correct maintainers I followed the way described by him to figure out maintainers.
I will add you to the maintainer list.

Following is the mailing list I collected until now. If I still miss someone, please let me know.

<<mwifiex mailing list>>
linux-wireless@...r.kernel.org
linux-kernel@...r.kernel.org;sharvari.harisangam@....com;yu-hao.lin@....com;tsung-hsien.hsieh@....com;kvalo@...nel.org;amitkarwar@...il.com;ganapathi017@...il.com;huxinming820@...il.com;davem@...emloft.net;edumazet@...gle.com;kuba@...nel.org;pabeni@...hat.com;francesco@...cini.it;briannorris@...omium.org

> 
> (Like I said earlier, I'm not exactly happy that y'all are failing to maintain this
> driver, but then insisting the community review and accept new features. At
> least if your paying customers will help out this process, the bargain is
> less-bad...)
> 

I think we will commit to the code we submitted. In fact, we will have QA to verify patches we submitted and we will continue to submit patches to fix issues reported by our QA or customers to use the code we submitted.

> Brian