linux-kernel - RE: [EXT] Re: [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to support iw61x

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:
 <PA4PR04MB9638824370878CB3BC426DBAD1812@PA4PR04MB9638.eurprd04.prod.outlook.com>
Date: Fri, 16 Aug 2024 05:32:27 +0000
From: David Lin <yu-hao.lin@....com>
To: Kalle Valo <kvalo@...nel.org>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"johannes@...solutions.net" <johannes@...solutions.net>,
	"briannorris@...omium.org" <briannorris@...omium.org>, "francesco@...cini.it"
	<francesco@...cini.it>, Pete Hsieh <tsung-hsien.hsieh@....com>
Subject: RE: [EXT] Re: [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to
 support iw61x

> From: Kalle Valo <kvalo@...nel.org>
> Sent: Thursday, August 15, 2024 5:36 PM
> To: David Lin <yu-hao.lin@....com>
> Cc: linux-wireless@...r.kernel.org; linux-kernel@...r.kernel.org;
> johannes@...solutions.net; briannorris@...omium.org;
> francesco@...cini.it; Pete Hsieh <tsung-hsien.hsieh@....com>
> Subject: [EXT] Re: [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to support
> iw61x
> 
> David Lin <yu-hao.lin@....com> writes:
> 
> > I found Nxpwifi patch v2 is put in "Deferred" state quickly.
> 
> The way I use patchwork states is described here:
> 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwireles
> s.wiki.kernel.org%2Fen%2Fdevelopers%2Fdocumentation%2Fsubmittingpatch
> es%23checking_state_of_patches_from_patchwork&data=05%7C02%7Cyu-ha
> o.lin%40nxp.com%7C8d360234b61d4e2c13e108dcbd0da0a4%7C686ea1d3bc
> 2b4c6fa92cd99c5c301635%7C0%7C0%7C638593113436356863%7CUnknown
> %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW
> wiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=1XA1Ax66zhnU72efN0wAghLJ
> %2F3DR1%2B8PAxXkiHphA%2FY%3D&reserved=0
> 
> Basically I try to follow the "Inbox Zero" method and keep the amount of
> patches in New state (my "inbox") low and the Deferred state is my todo list.
> 
> > Patch v2 is mainly to address the comments from Johannes and it
> > actually took quite some efforts. We understand there are areas to
> > improve and we are committed to continue enhance/maintain the driver.
> >
> > Could you let me know your plan for reviewing Nxpwifi?
> 
> Reviewing new drivers take a lot of time, at the moment I'm following what
> other reviewers say before I'll look at it myself. The process is so slow and
> patience is needed.

Understood.

> 
> The last thing I want to see that once the driver is accepted NXP disappears
> and we end up having an unmaintained driver. Way too many companies do
> that.
> 

Yes, we are committed to maintaining nxpwifi.

> > Is there anything we can do to move this forward?
> 
> Yes, get involved with the community and help us, don't just expect that we
> do everything for you gratis. Especially helping Brian with mwifiex
> review/testing helps us (we get a better driver) and also helps you (you learn
> how the community works and you gain trust in the community).
> 

Yes, we will continue to help to maintain mwifiex, also we will like to involve and learn how
the community works.

> An excellent example is Realtek. Few years back Realtek was not involved
> with upstream development at all. But now Ping is doing an awesome job
> with maintaining ALL Realtek drivers, including the old drivers, and I even
> trust him so much that I pull directly from this tree. This is what NXP should
> aim for.
> 
> --
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchw
> ork.kernel.org%2Fproject%2Flinux-wireless%2Flist%2F&data=05%7C02%7Cyu-
> hao.lin%40nxp.com%7C8d360234b61d4e2c13e108dcbd0da0a4%7C686ea1d3
> bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638593113436367796%7CUnknow
> n%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
> WwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=4ly%2Bien1%2FscxRSdEdN0C
> hvRMH%2Bh8kbYfEKbjxWyqodw%3D&reserved=0
> 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwireles
> s.wiki.kernel.org%2Fen%2Fdevelopers%2Fdocumentation%2Fsubmittingpatch
> es&data=05%7C02%7Cyu-hao.lin%40nxp.com%7C8d360234b61d4e2c13e108
> dcbd0da0a4%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638593
> 113436374405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=va
> i2UN%2BKu2I5wKfmUoL8LEk7qBXmIuIK0eB4rtwoRDs%3D&reserved=0

Thanks for the information.

Thanks,
David