From: Linus Torvalds <torvalds@linux-foundation.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Emese Revfy <re.emese@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [GIT PULL 2/2] Kconfig updates for v5.10-rc1
Date: Wed, 2 Dec 2020 12:13:31 -0800 [thread overview]
Message-ID: <CAHk-=whfP8CBZGVKzuES9wU2BKTEdUTUhMMW-G90vxdMR8Zi0w@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQGHjLYteCt+8BXSY-5CB0gaO1JtHY-SpPFrfdchoHKrQ@mail.gmail.com>
On Wed, Dec 2, 2020 at 4:54 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> Just a nit:
> Now that the test code does not include any header,
> you can also delete
> "-I $srctree/gcc-plugins -I $gccplugins_dir/include"
Ahh,m yes.
It sounds like we might be able to delete the build test entirely if
we just always expect to have a recent enough gcc.
Testing the headers for existence would presumably still be needed,
just to verify "do we have plugin support installed at all".
But I'm not planning on applying this directly - I find the config
overhead to be a bit annoying, but it's not like it is _objectively_
really a problem. More of a personal hangup ;)
Linus
next prev parent reply other threads:[~2020-12-02 20:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 13:49 [GIT PULL 2/2] Kconfig updates for v5.10-rc1 Masahiro Yamada
2020-10-22 20:25 ` pr-tracker-bot
2020-11-27 21:08 ` Linus Torvalds
2020-11-27 21:15 ` Linus Torvalds
2020-11-27 21:53 ` Linus Torvalds
2020-11-27 22:05 ` Linus Torvalds
2020-11-28 7:04 ` Masahiro Yamada
2020-11-28 18:28 ` Linus Torvalds
2020-12-02 0:55 ` Kees Cook
2020-12-02 12:53 ` Masahiro Yamada
2020-12-02 13:03 ` Masahiro Yamada
2020-12-02 18:58 ` Kees Cook
2020-12-02 20:13 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-22 13:47 Masahiro Yamada
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='CAHk-=whfP8CBZGVKzuES9wU2BKTEdUTUhMMW-G90vxdMR8Zi0w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@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;
as well as URLs for NNTP newsgroup(s).