From: Andrew Donnellan <ajd@linux.ibm.com>
To: Kees Cook <keescook@chromium.org>,
linuxppc-dev@lists.ozlabs.org, linux-hardening@vger.kernel.org
Cc: erhard_f@mailbox.org, yury.norov@gmail.com
Subject: Re: [PATCH] gcc-plugins: Undefine LATENT_ENTROPY_PLUGIN when plugin disabled for a file
Date: Wed, 17 Aug 2022 13:09:44 +1000 [thread overview]
Message-ID: <8c320ae1b88fd72dda3da6086d0742d3289f002f.camel@linux.ibm.com> (raw)
In-Reply-To: <166067790682.7084.237943534143309650.b4-ty@chromium.org>
On Tue, 2022-08-16 at 12:25 -0700, Kees Cook wrote:
> Applied to for-next/hardening, thanks!
>
> [1/1] gcc-plugins: Undefine LATENT_ENTROPY_PLUGIN when plugin
> disabled for a file
> https://git.kernel.org/kees/c/2d08c71d2c79
>
Thanks Kees!
Can we make sure this lands in rc2?
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
prev parent reply other threads:[~2022-08-17 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 5:17 [PATCH] gcc-plugins: Undefine LATENT_ENTROPY_PLUGIN when plugin disabled for a file Andrew Donnellan
2022-08-16 12:14 ` Yury Norov
2022-08-17 3:09 ` Andrew Donnellan
2022-08-16 19:25 ` Kees Cook
2022-08-17 3:09 ` Andrew Donnellan [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=8c320ae1b88fd72dda3da6086d0742d3289f002f.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=erhard_f@mailbox.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yury.norov@gmail.com \
/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).