From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: Brian Norris <briannorris@chromium.org>,
Francesco Dolcini <francesco@dolcini.it>,
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 v3 00/12] mwifiex: two fixes and cleanup
Date: Mon, 2 Dec 2024 16:41:01 +0100 [thread overview]
Message-ID: <Z03VDfTImax7lu_p@pengutronix.de> (raw)
In-Reply-To: <87ldwyumvq.fsf@kernel.org>
On Mon, Dec 02, 2024 at 05:26:33PM +0200, Kalle Valo wrote:
> Sascha Hauer <s.hauer@pengutronix.de> writes:
>
> > These are a few patches broken out from [1]. Kalle requested to limit
> > the number of patches per series to approximately 12 and Francesco to
> > move the fixes to the front of the series, so here we go.
> >
> > First two patches are fixes. First one is for host mlme support which
> > currently is in wireless-next, so no stable tag needed, second one has a
> > stable tag.
>
> Are you sure? Apparently we didn't take any patches to wireless-next
> during this merge window (ie. last two weeks), so everything which is in
> wireless-next should be in v6.13-rc1, unless I'm missing something of
> course. Not a problem for me but wanted to point out anyway.
Forget this last sentence, I should have removed it. It was true for v1
of this series. 01/12 is already applied as 0d7c2194f17c7 ("wifi: mwifiex:
add missing locking for cfg80211 calls") and I should have dropped that
patch from this series.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-12-02 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 12:57 [PATCH v3 00/12] mwifiex: two fixes and cleanup Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 01/12] wifi: mwifiex: add missing locking Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 02/12] wifi: mwifiex: fix MAC address handling Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 03/12] wifi: mwifiex: deduplicate code in mwifiex_cmd_tx_rate_cfg() Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 04/12] wifi: mwifiex: use adapter as context pointer for mwifiex_hs_activated_event() Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 05/12] wifi: mwifiex: drop unnecessary initialization Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 06/12] wifi: mwifiex: make region_code_mapping_t const Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 07/12] wifi: mwifiex: pass adapter to mwifiex_dnld_cmd_to_fw() Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 08/12] wifi: mwifiex: simplify mwifiex_setup_ht_caps() Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 09/12] wifi: mwifiex: fix indention Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 10/12] wifi: mwifiex: make locally used function static Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 11/12] wifi: mwifiex: move common settings out of switch/case Sascha Hauer
2024-12-02 12:58 ` [PATCH v3 12/12] wifi: mwifiex: drop asynchronous init waiting code Sascha Hauer
2024-12-02 15:26 ` [PATCH v3 00/12] mwifiex: two fixes and cleanup Kalle Valo
2024-12-02 15:41 ` Sascha Hauer [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=Z03VDfTImax7lu_p@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kernel@pengutronix.de \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 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.