From: Brian Norris <briannorris@chromium.org>
To: George Valkov <gvalkov@gmail.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Dan Carpenter <error27@gmail.com>,
johannes.berg@intel.com, kees@kernel.org, bhelgaas@google.com,
s.kerkmann@pengutronix.de, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] wifi: mwifiex: replace one-element arrays with flexible array members
Date: Tue, 11 Aug 2026 14:39:41 -0700 [thread overview]
Message-ID: <anuWnc6MKyT8J-O6@google.com> (raw)
In-Reply-To: <CADOrJmaRjN4XEZAyaWR_4g2vTbmmaSeFdzJ7r2ncsZkbvAxQsQ@mail.gmail.com>
On Mon, Jul 27, 2026 at 03:16:54PM +0300, George Valkov wrote:
> Any update on the progress? Do I need to do or change anything?
Your patch was merged for the next release on July 21. This process is
(unfortunately, IMO) silent in wireless land, but it is reflected in
Patchwork. You can see its status here:
https://patchwork.kernel.org/project/linux-wireless/patch/20260716001728.57799-1-gvalkov@gmail.com/
You can also see, for example, that v1 was marked "superseded":
https://patchwork.kernel.org/project/linux-wireless/patch/20260712222334.7134-1-gvalkov@gmail.com/
You didn't send v2 in the appropriate format, so it didn't get logged on
Patchwork.
Regards,
Brian
next prev parent reply other threads:[~2026-08-11 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 22:23 [PATCH] wifi: mwifiex: replace one-element arrays with flexible array members Georgi Valkov
2026-07-15 16:14 ` Francesco Dolcini
2026-07-15 16:35 ` Kees Cook
2026-07-15 22:59 ` George Valkov
2026-07-16 0:17 ` [PATCH v3] " Georgi Valkov
2026-07-16 6:16 ` Francesco Dolcini
2026-07-16 6:27 ` Dan Carpenter
2026-07-16 6:32 ` Francesco Dolcini
2026-07-16 6:55 ` Dan Carpenter
2026-07-16 8:09 ` George Valkov
2026-07-27 12:16 ` George Valkov
2026-08-11 21:39 ` Brian Norris [this message]
2026-07-16 6:42 ` George Valkov
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=anuWnc6MKyT8J-O6@google.com \
--to=briannorris@chromium.org \
--cc=bhelgaas@google.com \
--cc=error27@gmail.com \
--cc=francesco@dolcini.it \
--cc=gvalkov@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.kerkmann@pengutronix.de \
--cc=stable@vger.kernel.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 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.