From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Wetzel <alexander@wetzel-home.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Patch "wifi: mac80211: remove debugfs dir for virtual monitor" has been added to the 6.13-stable tree
Date: Tue, 8 Apr 2025 08:44:40 +0200 [thread overview]
Message-ID: <2025040829-zone-barman-1690@gregkh> (raw)
In-Reply-To: <ce57a679-9449-479a-aaef-58226c3445cd@wetzel-home.de>
On Mon, Apr 07, 2025 at 06:23:27PM +0200, Alexander Wetzel wrote:
> On 4/7/25 17:25, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > wifi: mac80211: remove debugfs dir for virtual monitor
> >
> > to the 6.13-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > wifi-mac80211-remove-debugfs-dir-for-virtual-monitor.patch
> > and it can be found in the queue-6.13 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
>
> The commit here is causing a sparse warning. Please always add commit
> 861d0445e72e ("wifi: mac80211: Fix sparse warning for monitor_sdata") when
> you backport this patch to avoid that. (So far I got the backport
> notification for 6.12 and 6.13.)
>
> It's also no big deal when you decide to not backport this patch.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-04-08 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250407152519.3128878-1-sashal@kernel.org>
2025-04-07 16:23 ` Patch "wifi: mac80211: remove debugfs dir for virtual monitor" has been added to the 6.13-stable tree Alexander Wetzel
2025-04-08 6:44 ` Greg KH [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=2025040829-zone-barman-1690@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander@wetzel-home.de \
--cc=johannes@sipsolutions.net \
--cc=stable-commits@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox