linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"briannorris@chromium.org" <briannorris@chromium.org>,
	"francesco@dolcini.it" <francesco@dolcini.it>,
	 Pete Hsieh <tsung-hsien.hsieh@nxp.com>
Subject: Re: [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to support iw61x
Date: Thu, 15 Aug 2024 12:35:35 +0300	[thread overview]
Message-ID: <87frr6yvq0.fsf@kernel.org> (raw)
In-Reply-To: <PA4PR04MB963858E759C8F61402B2275AD1872@PA4PR04MB9638.eurprd04.prod.outlook.com> (David Lin's message of "Wed, 14 Aug 2024 03:47:03 +0000")

David Lin <yu-hao.lin@nxp.com> writes:

> I found Nxpwifi patch v2 is put in "Deferred" state quickly.

The way I use patchwork states is described here:

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#checking_state_of_patches_from_patchwork

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.

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.

> 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).

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://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-08-15  9:35 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  9:44 [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to support iw61x David Lin
2024-08-09  9:44 ` [PATCH v2 01/43] wifi: nxpwifi: add 11ac.c David Lin
2024-08-09  9:44 ` [PATCH v2 02/43] wifi: nxpwifi: add 11ac.h David Lin
2024-08-09  9:44 ` [PATCH v2 03/43] wifi: nxpwifi: add 11h.c David Lin
2024-08-09  9:44 ` [PATCH v2 04/43] wifi: nxpwifi: add 11n_aggr.c David Lin
2024-08-09  9:44 ` [PATCH v2 05/43] wifi: nxpwifi: add 11n_aggr.h David Lin
2024-08-09  9:44 ` [PATCH v2 06/43] wifi: nxpwifi: add 11n.c David Lin
2024-08-09  9:44 ` [PATCH v2 07/43] wifi: nxpwifi: add 11n.h David Lin
2024-08-09  9:44 ` [PATCH v2 08/43] wifi: nxpwifi: add 11n_rxreorder.c David Lin
2024-08-09  9:44 ` [PATCH v2 09/43] wifi: nxpwifi: add 11n_rxreorder.h David Lin
2024-08-09  9:45 ` [PATCH v2 10/43] wifi: nxpwifi: add cfg80211.c David Lin
2024-08-09  9:45 ` [PATCH v2 11/43] wifi: nxpwifi: add cfg80211.h David Lin
2024-08-09  9:45 ` [PATCH v2 12/43] wifi: nxpwifi: add cfg.h David Lin
2024-08-09  9:45 ` [PATCH v2 13/43] wifi: nxpwifi: add cfp.c David Lin
2024-08-09  9:45 ` [PATCH v2 14/43] wifi: nxpwifi: add cmdevt.c David Lin
2024-08-09  9:45 ` [PATCH v2 15/43] wifi: nxpwifi: add cmdevt.h David Lin
2024-08-09  9:45 ` [PATCH v2 16/43] wifi: nxpwifi: add debugfs.c David Lin
2024-08-09  9:45 ` [PATCH v2 17/43] wifi: nxpwifi: add decl.h David Lin
2024-08-09  9:45 ` [PATCH v2 18/43] wifi: nxpwifi: add ethtool.c David Lin
2024-08-09  9:45 ` [PATCH v2 19/43] wifi: nxpwifi: add fw.h David Lin
2024-08-09  9:45 ` [PATCH v2 20/43] wifi: nxpwifi: add ie.c David Lin
2024-08-09  9:45 ` [PATCH v2 21/43] wifi: nxpwifi: add init.c David Lin
2024-08-09  9:45 ` [PATCH v2 22/43] wifi: nxpwifi: add join.c David Lin
2024-08-09  9:45 ` [PATCH v2 23/43] wifi: nxpwifi: add main.c David Lin
2024-08-09  9:45 ` [PATCH v2 24/43] wifi: nxpwifi: add main.h David Lin
2024-08-09  9:45 ` [PATCH v2 25/43] wifi: nxpwifi: add scan.c David Lin
2024-08-09  9:45 ` [PATCH v2 26/43] wifi: nxpwifi: add sdio.c David Lin
2024-08-09  9:45 ` [PATCH v2 27/43] wifi: nxpwifi: add sdio.h David Lin
2024-08-09  9:45 ` [PATCH v2 28/43] wifi: nxpwifi: add sta_cfg.c David Lin
2024-08-09  9:45 ` [PATCH v2 29/43] wifi: nxpwifi: add sta_cmd.c David Lin
2024-08-09  9:45 ` [PATCH v2 30/43] wifi: nxpwifi: add sta_event.c David Lin
2024-08-09  9:45 ` [PATCH v2 31/43] wifi: nxpwifi: add sta_rx.c David Lin
2024-08-09  9:45 ` [PATCH v2 32/43] wifi: nxpwifi: add sta_tx.c David Lin
2024-08-09  9:45 ` [PATCH v2 33/43] wifi: nxpwifi: add txrx.c David Lin
2024-08-09  9:45 ` [PATCH v2 34/43] wifi: nxpwifi: add uap_cmd.c David Lin
2024-08-09  9:45 ` [PATCH v2 35/43] wifi: nxpwifi: add uap_event.c David Lin
2024-08-09  9:45 ` [PATCH v2 36/43] wifi: nxpwifi: add uap_txrx.c David Lin
2024-08-09  9:45 ` [PATCH v2 37/43] wifi: nxpwifi: add util.c David Lin
2024-08-09  9:45 ` [PATCH v2 38/43] wifi: nxpwifi: add util.h David Lin
2024-08-09  9:45 ` [PATCH v2 39/43] wifi: nxpwifi: add wmm.c David Lin
2024-08-09  9:45 ` [PATCH v2 40/43] wifi: nxpwifi: add wmm.h David Lin
2024-08-14 18:48   ` Greg KH
2024-08-15  1:52     ` [EXT] " David Lin
2024-08-15  5:08       ` Greg KH
2024-08-15  6:20         ` David Lin
2024-08-15  6:23           ` David Lin
2024-08-15  6:57           ` Greg KH
2024-08-15  9:51           ` Kalle Valo
2024-08-16  1:39             ` David Lin
2024-08-15  9:43         ` Kalle Valo
2024-08-15  9:58           ` Greg KH
2024-08-15 11:44             ` Kalle Valo
2024-08-09  9:45 ` [PATCH v2 41/43] wifi: nxpwifi: add nxp sdio vendor id and iw61x device id David Lin
2024-08-09  9:45 ` [PATCH v2 42/43] wifi: nxpwifi: add Makefile and Kconfig files for nxpwifi compilation David Lin
2024-08-09  9:45 ` [PATCH v2 43/43] wifi: nxpwifi: add nxpwifi related information to MAINTAINERS David Lin
2024-08-14  3:47 ` [PATCH v2 00/43] wifi: nxpwifi: create nxpwifi to support iw61x David Lin
2024-08-15  9:35   ` Kalle Valo [this message]
2024-08-16  5:32     ` [EXT] " David Lin
2024-08-22 12:56 ` Sascha Hauer
2024-08-24 13:48   ` Francesco Dolcini
2024-08-26  2:30     ` [EXT] " David Lin
2024-08-26  7:43     ` Sascha Hauer
2024-08-25 20:37   ` Calvin Owens
2024-08-26  2:33     ` [EXT] " David Lin
2024-08-26  2:49       ` Calvin Owens
2024-08-26  2:56         ` David Lin
2024-08-26  5:30           ` Calvin Owens
2024-08-26  5:49             ` David Lin
2024-10-17  7:48   ` Kalle Valo
2024-12-11  3:52     ` [EXT] " David Lin
2025-01-10  5:31       ` Jeff Chen

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=87frr6yvq0.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tsung-hsien.hsieh@nxp.com \
    --cc=yu-hao.lin@nxp.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).