From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: <linux-kernel@vger.kernel.org>,
Amitkumar Karwar <amitkarwar@gmail.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>,
Xinming Hu <huxinming820@gmail.com>,
linux-wireless@vger.kernel.org,
Brian Norris <briannorris@chromium.org>
Subject: Re: [RFC PATCH v2 1/2] mwifiex: refactor mwifiex_parse_htinfo() for reuse
Date: Thu, 13 Dec 2018 14:55:45 +0000 (UTC) [thread overview]
Message-ID: <20181213145547.68F0260918@smtp.codeaurora.org> (raw)
In-Reply-To: <20181207001249.165477-1-briannorris@chromium.org>
Brian Norris <briannorris@chromium.org> wrote:
> This function converts some firmware-specific parameters into cfg80211
> 'rate_info' structures. It currently assumes it's dealing only with TX
> bitrate, but the RX bitrate looks to be the same, so refactor this
> function to be reusable.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
2 patches applied to wireless-drivers-next.git, thanks.
a256707fbd4b mwifiex: refactor mwifiex_parse_htinfo() for reuse
ed0b2b067bad mwifiex: add NL80211_STA_INFO_RX_BITRATE support
--
https://patchwork.kernel.org/patch/10717275/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-12-13 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 0:12 [RFC PATCH v2 1/2] mwifiex: refactor mwifiex_parse_htinfo() for reuse Brian Norris
2018-12-07 0:12 ` [RFC PATCH v2 2/2] mwifiex: add NL80211_STA_INFO_RX_BITRATE support Brian Norris
2018-12-07 10:50 ` Kalle Valo
2018-12-07 11:55 ` [EXT] " Ganapathi Bhat
2018-12-13 14:55 ` Kalle Valo [this message]
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=20181213145547.68F0260918@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=gbhat@marvell.com \
--cc=huxinming820@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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).