From: Kees Cook <keescook@chromium.org>
To: linux@roeck-us.net, masahiroy@kernel.org,
linux-hardening@vger.kernel.org
Cc: Kees Cook <keescook@chromium.org>,
lkp@intel.com, linux-kbuild@vger.kernel.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc-plugins: use KERNELVERSION for plugin version
Date: Tue, 24 May 2022 08:26:55 -0700 [thread overview]
Message-ID: <165340601337.1531311.10949376876252513636.b4-ty@chromium.org> (raw)
In-Reply-To: <20220524135541.1453693-1-masahiroy@kernel.org>
On Tue, 24 May 2022 22:55:41 +0900, Masahiro Yamada wrote:
> Commit 61f60bac8c05 ("gcc-plugins: Change all version strings match
> kernel") broke parallel builds.
>
> Instead of adding the dependency between GCC plugins and utsrelease.h,
> let's use KERNELVERSION, which does not require any build artifact.
>
> Another reason why I want to avoid utsrelease.h is because it depends
> on CONFIG_LOCALVERSION(_AUTO) and localversion* files.
>
> [...]
Ah, perfect; I appreciate the better solution! Applied to
for-next/hardening, thanks!
[1/1] gcc-plugins: use KERNELVERSION for plugin version
https://git.kernel.org/kees/c/d37aa2efc89b
--
Kees Cook
prev parent reply other threads:[~2022-05-24 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:55 [PATCH] gcc-plugins: use KERNELVERSION for plugin version Masahiro Yamada
2022-05-24 15:26 ` Kees Cook [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=165340601337.1531311.10949376876252513636.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.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.