From: Kalle Valo <kvalo@kernel.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"briannorris@chromium.org" <briannorris@chromium.org>,
"francesco@dolcini.it" <francesco@dolcini.it>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>,
Rafael Beims <rafael.beims@toradex.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme
Date: Wed, 10 Jul 2024 11:02:06 +0300 [thread overview]
Message-ID: <8734ohn08x.fsf@kernel.org> (raw)
In-Reply-To: <PA4PR04MB9638BD3D09017A786FC3DAECD1A42@PA4PR04MB9638.eurprd04.prod.outlook.com> (David Lin's message of "Wed, 10 Jul 2024 01:47:17 +0000")
David Lin <yu-hao.lin@nxp.com> writes:
> I found the state of this patch series had been changed to "Deferred".
>
> Since this patch series had been reviewed for a long period of time and
> reviewed, tested, and acked by members from community. I wonder what
> else should I do to let it be merged to mainline Linux kernel?
Most likely the merge window opens on Sunday and I didn't want to apply
the patchset last minute. So this has to wait v6.12.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-07-10 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 3:29 [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-04 3:30 ` [PATCH v11 1/2] wifi: mwifiex: add host mlme for client mode David Lin
2024-08-04 8:56 ` Kalle Valo
2024-07-04 3:30 ` [PATCH v11 2/2] wifi: mwifiex: add host mlme for AP mode David Lin
2024-07-08 19:26 ` Brian Norris
2024-07-09 2:26 ` [EXT] " David Lin
2024-07-10 1:47 ` [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-10 8:02 ` Kalle Valo [this message]
2024-07-11 1:33 ` [EXT] " David Lin
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=8734ohn08x.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafael.beims@toradex.com \
--cc=tsung-hsien.hsieh@nxp.com \
--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).