From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
stable <stable@vger.kernel.org>
Subject: Re: [stable] Security fixes for brcmfmac
Date: Tue, 28 May 2019 08:54:03 +0200 [thread overview]
Message-ID: <20190528065403.GC2623@kroah.com> (raw)
In-Reply-To: <1558992664.2631.12.camel@codethink.co.uk>
On Mon, May 27, 2019 at 10:31:04PM +0100, Ben Hutchings wrote:
> Please pick the following fixes to brcmfmac for the 4.14, 4.19, and 5.0
> stable branches:
>
> 1b5e2423164b brcmfmac: assure SSID length from firmware is limited
> a4176ec356c7 brcmfmac: add subtype check for event handling in data path
>
> They are also needed for earlier branches, but they don't apply cleanly
> so I will send patches later.
Thanks for letting me know, both now queued up.
greg k-h
prev parent reply other threads:[~2019-05-28 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 21:31 [stable] Security fixes for brcmfmac Ben Hutchings
2019-05-28 6:54 ` Greg Kroah-Hartman [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=20190528065403.GC2623@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).