From: Kees Cook <keescook@chromium.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Emese Revfy <re.emese@gmail.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-hardening@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Dan Li <ashimida@linux.alibaba.com>,
Ard Biesheuvel <ardb@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Nathan Chancellor <nathan@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH 2/2] gcc-plugins: Remove cyc_complexity
Date: Wed, 20 Oct 2021 12:11:29 -0700 [thread overview]
Message-ID: <202110201210.1F70546@keescook> (raw)
In-Reply-To: <CANiq72kveT40jX8GWjs1dy0o3YjowUGtGTddPb+da114sb+4iA@mail.gmail.com>
On Wed, Oct 20, 2021 at 07:48:55PM +0200, Miguel Ojeda wrote:
> On Wed, Oct 20, 2021 at 7:35 PM Kees Cook <keescook@chromium.org> wrote:
> >
> > - * Copyright 2011-2016 by Emese Revfy <re.emese@gmail.com>
>
> Perhaps we should Cc this address to give them notice.
Good point; I'm in the habit of that happening automatically as Emese
was a co-maintainer of the gcc-plugins. Sorry for the oversight here.
> Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
Thanks!
--
Kees Cook
next prev parent reply other threads:[~2021-10-20 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 17:35 [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule Kees Cook
2021-10-20 17:35 ` [PATCH 1/2] " Kees Cook
2021-10-20 17:44 ` Miguel Ojeda
2021-10-20 19:12 ` Kees Cook
2021-10-20 17:45 ` Nathan Chancellor
2021-10-20 19:15 ` Kees Cook
2021-10-20 17:35 ` [PATCH 2/2] gcc-plugins: Remove cyc_complexity Kees Cook
2021-10-20 17:48 ` Miguel Ojeda
2021-10-20 19:11 ` Kees Cook [this message]
2021-10-20 17:48 ` Nathan Chancellor
2021-10-20 19:10 ` Kees Cook
2021-10-20 17:50 ` [PATCH 0/2] gcc-plugins: Explicitly document purpose and deprecation schedule Nick Desaulniers
2021-10-21 10:28 ` Ard Biesheuvel
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=202110201210.1F70546@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=ashimida@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=re.emese@gmail.com \
--cc=serge@hallyn.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 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.