From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org, nbd@nbd.name, lorenzo@kernel.org,
ryder.lee@mediatek.com, shayne.chen@mediatek.com,
sean.wang@mediatek.com, matthias.bgg@gmail.com,
Bo.Jiao@mediatek.com, sujuan.chen@mediatek.com,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH wireless-next 2/3] wifi: mt76: switch to netif_napi_add_tx()
Date: Fri, 06 May 2022 08:32:41 +0300 [thread overview]
Message-ID: <87wnezxm2u.fsf@kernel.org> (raw)
In-Reply-To: <20220504163316.549648-3-kuba@kernel.org> (Jakub Kicinski's message of "Wed, 4 May 2022 09:33:15 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> Switch to the new API not requiring passing in NAPI_POLL_WEIGHT.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Felix, I'll assign this to me on patchwork and apply directly to
wireless-next.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org, nbd@nbd.name, lorenzo@kernel.org,
ryder.lee@mediatek.com, shayne.chen@mediatek.com,
sean.wang@mediatek.com, matthias.bgg@gmail.com,
Bo.Jiao@mediatek.com, sujuan.chen@mediatek.com,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH wireless-next 2/3] wifi: mt76: switch to netif_napi_add_tx()
Date: Fri, 06 May 2022 08:32:41 +0300 [thread overview]
Message-ID: <87wnezxm2u.fsf@kernel.org> (raw)
In-Reply-To: <20220504163316.549648-3-kuba@kernel.org> (Jakub Kicinski's message of "Wed, 4 May 2022 09:33:15 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> Switch to the new API not requiring passing in NAPI_POLL_WEIGHT.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Felix, I'll assign this to me on patchwork and apply directly to
wireless-next.
--
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-06 5:33 UTC|newest]
Thread overview: 13+ 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-04 16:33 ` Jakub Kicinski
2022-05-06 5:32 ` Kalle Valo [this message]
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 ` [PATCH wireless-next 0/3] wifi: netif_napi_add() conversions Kalle Valo
2022-05-05 15:54 ` 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=87wnezxm2u.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Bo.Jiao@mediatek.com \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.