From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next 0/3] wifi: netif_napi_add() conversions
Date: Thu, 05 May 2022 07:25:03 +0300 [thread overview]
Message-ID: <87a6bwzjvk.fsf@kernel.org> (raw)
In-Reply-To: <20220504163316.549648-1-kuba@kernel.org> (Jakub Kicinski's message of "Wed, 4 May 2022 09:33:13 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> Convert wifi callers to the new netif_napi_add() APIs.
>
> The callers passing 64 or NAPI_POLL_WEIGHT to the non-Tx flavor
> are left alone. I'm planning to include wifi drivers in the massive
> tree-wide patch/series which will drop the last argument from
> netif_napi_add(). Alternatively I can switch all of wifi to
> netif_napi_add_tx_weight() and back after the netif_napi_add()
> change makes its wait into wireless-next.
> Please LMK if you prefer that.
>
> Jakub Kicinski (3):
> wifi: wil6210: switch to netif_napi_add_tx()
> wifi: mt76: switch to netif_napi_add_tx()
> wifi: qtnfmac: switch to netif_napi_add_weight()
We don't use that "wifi:" prefix, otherwise looks good. Feel free to
take via your tree:
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-05-05 4:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 16:33 [PATCH wireless-next 0/3] wifi: netif_napi_add() conversions Jakub Kicinski
2022-05-04 16:33 ` [PATCH wireless-next 1/3] wifi: wil6210: switch to netif_napi_add_tx() Jakub Kicinski
2022-05-06 5:48 ` [wireless-next,1/3] " Kalle Valo
2022-05-04 16:33 ` [PATCH wireless-next 2/3] wifi: mt76: " Jakub Kicinski
2022-05-06 5:32 ` Kalle Valo
2022-05-04 16:33 ` [PATCH wireless-next 3/3] wifi: qtnfmac: switch to netif_napi_add_weight() Jakub Kicinski
2022-05-05 4:25 ` Kalle Valo [this message]
2022-05-05 15:54 ` [PATCH wireless-next 0/3] wifi: netif_napi_add() conversions Jakub Kicinski
2022-05-06 5:30 ` Kalle Valo
2022-05-09 11:14 ` Kalle Valo
2022-05-09 16:33 ` Jakub Kicinski
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=87a6bwzjvk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).