From: Brian Norris <briannorris@chromium.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
David Lin <yu-hao.lin@nxp.com>,
kernel@pengutronix.de,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH wireless-next v5 00/10] mwifiex: cleanups
Date: Tue, 25 Mar 2025 15:26:40 -0700 [thread overview]
Message-ID: <Z-MtoOCLX2_1GztI@google.com> (raw)
In-Reply-To: <20250324-mwifiex-cleanup-1-v5-0-1128a2be02af@pengutronix.de>
On Mon, Mar 24, 2025 at 02:24:01PM +0100, Sascha Hauer wrote:
> This contains several cleanup patches for the mwifiex driver. I dropped
> the MAC address fixing patch this time as it needs more discussion, but
> the remaining patches sent here are nearly unchanged from v1 and should
> be good to go.
Thanks! For patches 1-9:
Acked-by: Brian Norris <briannorris@chromium.org>
I had some issues with patch 10.
If you respin before Johannes applies any of these, feel free to carry
my Acked-by.
Brian
prev parent reply other threads:[~2025-03-25 22:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 13:24 [PATCH wireless-next v5 00/10] mwifiex: cleanups Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 01/10] wifi: mwifiex: deduplicate code in mwifiex_cmd_tx_rate_cfg() Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 02/10] wifi: mwifiex: use adapter as context pointer for mwifiex_hs_activated_event() Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 03/10] wifi: mwifiex: drop unnecessary initialization Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 04/10] wifi: mwifiex: make region_code_mapping_t const Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 05/10] wifi: mwifiex: pass adapter to mwifiex_dnld_cmd_to_fw() Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 06/10] wifi: mwifiex: simplify mwifiex_setup_ht_caps() Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 07/10] wifi: mwifiex: fix indention Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 08/10] wifi: mwifiex: make locally used function static Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 09/10] wifi: mwifiex: move common settings out of switch/case Sascha Hauer
2025-03-24 13:24 ` [PATCH wireless-next v5 10/10] wifi: mwifiex: drop asynchronous init waiting code Sascha Hauer
2025-03-25 22:25 ` Brian Norris
2025-03-26 10:59 ` Sascha Hauer
2025-03-25 22:26 ` Brian Norris [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=Z-MtoOCLX2_1GztI@google.com \
--to=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=johannes.berg@intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--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).