From: Greg KH <gregkh@linuxfoundation.org>
To: Magal Baz <mbaz@fb.com>
Cc: "aspriel@gmail.com" <aspriel@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"security@kernel.org" <security@kernel.org>
Subject: Re: Vulnerabilities in the brcmfmac driver
Date: Mon, 22 Aug 2022 21:33:21 +0200 [thread overview]
Message-ID: <YwPaASokqw0eunUj@kroah.com> (raw)
In-Reply-To: <97D835D2-29C5-4C86-8602-4C02C61DB28C@fb.com>
On Mon, Aug 22, 2022 at 05:12:58PM +0000, Magal Baz wrote:
>
> Please see the details in the attached PDF file.
For obvious reasons, we can't open unsolicited .pdf files, nor should
you ever put anything that should just be a normal text message, in that
for a kernel bug report :)
Also, as you sent this to public lists, no need to get
security@kernel.org involved, the normal bug report / fixup process can
happen here now.
thanks,
greg k-h
next parent reply other threads:[~2022-08-22 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97D835D2-29C5-4C86-8602-4C02C61DB28C@fb.com>
2022-08-22 19:33 ` Greg KH [this message]
[not found] ` <03D5D6F4-4471-4379-BF53-464DAA37C4B2@fb.com>
2022-08-22 19:49 ` Vulnerabilities in the brcmfmac driver Greg KH
2022-08-22 19:51 ` Greg KH
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=YwPaASokqw0eunUj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mbaz@fb.com \
--cc=security@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.