From: Ryder Lee <ryder.lee-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: nbd-Vt+b4OUoWG0@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
roychl666-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/2] remove qid dependency from mt76-core code
Date: Mon, 18 Feb 2019 10:32:39 +0800 [thread overview]
Message-ID: <1550457159.18089.5.camel@mtkswgap22> (raw)
In-Reply-To: <cover.1550336347.git.lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Sat, 2019-02-16 at 18:47 +0100, lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org wrote:
> From: Lorenzo Bianconi <lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
> Move queue id dependency in driver specific tx queue initialization code
> since new chipsets rely on a different tx queue enumeration scheme.
> Add the possibility to specify qid in mt76_tx routine
>
> Lorenzo Bianconi (2):
> mt76: add qid parameter to mt76_tx signature
> mt76: move txq qid dependency in driver specific code
>
> drivers/net/wireless/mediatek/mt76/mac80211.c | 27 +++++++++++-------
> drivers/net/wireless/mediatek/mt76/mt76.h | 14 ++++++++--
> .../net/wireless/mediatek/mt76/mt76x02_txrx.c | 8 +++++-
> .../net/wireless/mediatek/mt76/mt76x02_util.c | 2 ++
> drivers/net/wireless/mediatek/mt76/tx.c | 28 +++++--------------
> 5 files changed, 45 insertions(+), 34 deletions(-)
>
Thanks. This will help us to develop the new chipsets more easily.
Acked-by: Ryder Lee <ryder.lee-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
parent reply other threads:[~2019-02-18 2:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <cover.1550336347.git.lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>]
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=1550457159.18089.5.camel@mtkswgap22 \
--to=ryder.lee-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=nbd-Vt+b4OUoWG0@public.gmane.org \
--cc=roychl666-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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