From: Sudip Mukherjee <sudipm.mukherjee@gmail•com>
To: Kees Cook <keescook@chromium•org>
Cc: Michal Marek <mmarek@suse•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Emese Revfy <re.emese@gmail•com>,
Paul Gortmaker <paul.gortmaker@windriver•com>,
Linux-Next <linux-next@vger•kernel.org>,
linux-kernel@vger•kernel.org,
kernel-hardening@lists•openwall.com
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST
Date: Mon, 13 Jun 2016 08:52:10 +0100 [thread overview]
Message-ID: <20160613075210.GB2031@sudip-tp> (raw)
In-Reply-To: <20160611161212.GA29370@www.outflux.net>
On Sat, Jun 11, 2016 at 09:12:12AM -0700, Kees Cook wrote:
> Since adding the gcc plugin development headers is required for the
> gcc plugin support, we should ease into this new kernel build dependency
> more slowly. For now, disable the gcc plugins under COMPILE_TEST so that
> all*config builds will skip it.
But don't you think that people who are actually building the kernel
with allmodconfig or allyesconfig and/or with COMPILE_TEST enabled are
just doing that to build test the kernel. Atleast for me, when I am
testing i will always do allmodconfig but when I am building which is
to be deployed somewhere then I am building with a particular config.
Regards
Sudip
next prev parent reply other threads:[~2016-06-13 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 16:12 [PATCH] gcc-plugins: disable under COMPILE_TEST Kees Cook
2016-06-11 16:29 ` Paul Gortmaker
2016-06-12 22:12 ` Emese Revfy
2016-06-12 22:25 ` Kees Cook
2016-06-13 0:18 ` Emese Revfy
2016-06-13 18:32 ` Austin S. Hemmelgarn
2016-06-13 20:11 ` Kees Cook
2016-06-14 2:01 ` Michael Ellerman
2016-06-13 7:52 ` Sudip Mukherjee [this message]
2016-06-13 8:40 ` Sedat Dilek
2016-06-13 20:15 ` 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=20160613075210.GB2031@sudip-tp \
--to=sudipm.mukherjee@gmail$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=kernel-hardening@lists$(echo .)openwall.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mmarek@suse$(echo .)com \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=re.emese@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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