From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefan Bühler" <stefan.buehler@tik.uni-stuttgart.de>
Cc: linux-wireless@vger.kernel.org, "Stefan Bühler" <source@stbuehler.de>
Subject: Re: [PATCH] cfg80211: fix double-free after changing network namespace
Date: Wed, 04 Dec 2019 09:50:21 +0100 [thread overview]
Message-ID: <4a007a507788461348a68076b2a1c40dff9c6de3.camel@sipsolutions.net> (raw)
In-Reply-To: <22d78eff-9975-e2eb-5093-b19f93831bce@tik.uni-stuttgart.de>
On Wed, 2019-12-04 at 09:26 +0100, Stefan Bühler wrote:
>
> Any status update for this? Anything I can do? Should I resubmit this
> with "Cc: stable@vger.kernel.org"?
No, it's fine, but we're in the middle of the merge window, I'm waiting
for some merge backs etc.
johannes
prev parent reply other threads:[~2019-12-04 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 10:05 [PATCH] cfg80211: fix double-free after changing network namespace Stefan Bühler
2019-11-26 10:12 ` Stefan Bühler
2019-11-26 15:55 ` Kalle Valo
2019-12-04 8:26 ` Stefan Bühler
2019-12-04 8:50 ` Johannes Berg [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=4a007a507788461348a68076b2a1c40dff9c6de3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=source@stbuehler.de \
--cc=stefan.buehler@tik.uni-stuttgart.de \
/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).