[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160613075210.GB2031@sudip-tp>
Date: Mon, 13 Jun 2016 08:52:10 +0100
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: Michal Marek <mmarek@...e.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Emese Revfy <re.emese@...il.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Linux-Next <linux-next@...r.kernel.org>,
linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
