[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kCQa7_3JkUqO2=mdj+P2zcjPYJUai0oip5DN7Aaq_ySQ@mail.gmail.com>
Date: Wed, 20 Oct 2021 19:44:19 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Jonathan Corbet <corbet@....net>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nathan Chancellor <nathan@...nel.org>,
linux-hardening@...r.kernel.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
llvm@...ts.linux.dev, Dan Li <ashimida@...ux.alibaba.com>,
Ard Biesheuvel <ardb@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] gcc-plugins: Explicitly document purpose and
deprecation schedule
On Wed, Oct 20, 2021 at 7:35 PM Kees Cook <keescook@...omium.org> wrote:
>
> +Purpose
> +=======
Sounds good to me.
> config GCC_PLUGIN_SANCOV
> bool
> + # Plugin can be removed once the kernel only supports GCC 6.1.0+
Since we are just giving the major in the other cases below, I would
just say GCC 6+ here (the numbering scheme changed in GCC 5 already).
Thanks for adding the versions, by the way -- this is useful long-term
and not always done for other things...
Reviewed-by: Miguel Ojeda <ojeda@...nel.org>
Cheers,
Miguel
Powered by blists - more mailing lists