public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Emese Revfy <re.emese@gmail.com>,
	linux-hardening@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gcc-plugins: remove code for GCC versions older than 4.9
Date: Fri, 4 Dec 2020 14:06:52 -0800	[thread overview]
Message-ID: <202012041403.792DE050C@keescook> (raw)
In-Reply-To: <CAK7LNAQxS2Zn3O4Q0Ca5KgoyEwW5_5DtPDZoXAH+dxbki7dmLg@mail.gmail.com>

On Thu, Dec 03, 2020 at 06:35:38PM +0900, Masahiro Yamada wrote:
> On Thu, Dec 3, 2020 at 4:01 AM Kees Cook <keescook@chromium.org> wrote:
> >
> > On Wed, Dec 02, 2020 at 10:49:29PM +0900, Masahiro Yamada wrote:
> > > Documentation/process/changes.rst says the minimal GCC version is 4.9.
> > > Hence, BUILDING_GCC_VERSION is greater than or equal to 4009.
> > >
> > > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> >
> > Acked-by: Kees Cook <keescook@chromium.org>
> >
> > Do you want to carry this in the kbuild tree, or would you like me to
> > pick it up?
> >
> > Thanks!
> >
> > --
> > Kees Cook
> 
> 
> Please pick it up.

Sounds good. Thanks!

Also, Emese, I haven't seen an email from you to LKML in almost 3
years. If you're interested in staying on CC for GCC plugin stuff,
please let me know. If not, I can update the MAINTAINERS file to reflect
reality. :)

-- 
Kees Cook

  reply	other threads:[~2020-12-04 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 13:49 [PATCH] gcc-plugins: remove code for GCC versions older than 4.9 Masahiro Yamada
2020-12-02 19:01 ` Kees Cook
2020-12-03  9:35   ` Masahiro Yamada
2020-12-04 22:06     ` Kees Cook [this message]
2020-12-04 23:46 ` Kees Cook

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=202012041403.792DE050C@keescook \
    --to=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=re.emese@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