Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2017-06-23 Thread Tony Breeds
On Fri, Jun 23, 2017 at 03:43:58PM +1000, Michael Ellerman wrote: > [Old thread just popped up in my inbox] > > Kees Cook writes: > > On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker > > wrote: > >> On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: > >>> Hi, > >>> > >>> I'd like to get the GCC plu

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2017-06-23 Thread Kees Cook
On Thu, Jun 22, 2017 at 10:43 PM, Michael Ellerman wrote: > [Old thread just popped up in my inbox] > > Kees Cook writes: >> On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker >> wrote: >>> On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: Hi, I'd like to get the GCC plugins building

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2017-06-22 Thread Michael Ellerman
[Old thread just popped up in my inbox] Kees Cook writes: > On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker > wrote: >> On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: >>> Hi, >>> >>> I'd like to get the GCC plugins building under >>> allyesconfig/allmodconfig for -next soon (with the intention

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2017-06-22 Thread Kees Cook
*thread necromancy* On Fri, Dec 9, 2016 at 11:40 AM, Linus Torvalds wrote: > On Fri, Dec 9, 2016 at 11:12 AM, Kees Cook wrote: >> I'm starting to wonder if we need to expose the compiler version to >> Kconfig so that "all*config" builds for earlier compiler will >> automatically leave things lik

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-16 Thread Kees Cook
On Sat, Dec 10, 2016 at 8:45 AM, Emese Revfy wrote: > On Fri, 9 Dec 2016 11:12:18 -0800 > Kees Cook wrote: > >> On Fri, Dec 9, 2016 at 2:40 AM, Arnd Bergmann wrote: >> > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: >> > >> >> If you have a moment, applying 215e2aa6c024[1] and r

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-10 Thread Emese Revfy
On Fri, 9 Dec 2016 11:12:18 -0800 Kees Cook wrote: > On Fri, Dec 9, 2016 at 2:40 AM, Arnd Bergmann wrote: > > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > > > >> If you have a moment, applying 215e2aa6c024[1] and reverting > >> a519167e753e for an allyesconfig/allmodconfig bu

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread kugan
On 10/12/16 07:35, Arnd Bergmann wrote: On Friday, December 9, 2016 11:13:20 AM CET Kees Cook wrote: On Fri, Dec 9, 2016 at 3:33 AM, Arnd Bergmann wrote: On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: If you have a moment, applying 215e2aa6c024[1] and reverting a519167e753e

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Arnd Bergmann
On Friday, December 9, 2016 11:13:20 AM CET Kees Cook wrote: > On Fri, Dec 9, 2016 at 3:33 AM, Arnd Bergmann wrote: > > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > >> If you have a moment, applying 215e2aa6c024[1] and reverting > >> a519167e753e for an allyesconfig/allmodconfi

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Linus Torvalds
On Fri, Dec 9, 2016 at 11:12 AM, Kees Cook wrote: > > I'm starting to wonder if we need to expose the compiler version to > Kconfig so that "all*config" builds for earlier compiler will > automatically leave things like plugins off. But I have no idea what > the right approach for that might be.

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Kees Cook
On Fri, Dec 9, 2016 at 3:33 AM, Arnd Bergmann wrote: > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: >> Hi, >> >> I'd like to get the GCC plugins building under >> allyesconfig/allmodconfig for -next soon (with the intention of >> landing the change in v4.11). Specifically, I inte

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Kees Cook
On Fri, Dec 9, 2016 at 2:40 AM, Arnd Bergmann wrote: > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > >> If you have a moment, applying 215e2aa6c024[1] and reverting >> a519167e753e for an allyesconfig/allmodconfig build should let you >> know if things are working correctly with

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Arnd Bergmann
On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > Hi, > > I'd like to get the GCC plugins building under > allyesconfig/allmodconfig for -next soon (with the intention of > landing the change in v4.11). Specifically, I intend to revert > a519167e753e ("gcc-plugins: disable under COM

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-09 Thread Arnd Bergmann
On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > If you have a moment, applying 215e2aa6c024[1] and reverting > a519167e753e for an allyesconfig/allmodconfig build should let you > know if things are working correctly with headers installed. If anyone > sees any problems, please le

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-08 Thread Kees Cook
On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker wrote: > On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: >> Hi, >> >> I'd like to get the GCC plugins building under >> allyesconfig/allmodconfig for -next soon (with the intention of >> landing the change in v4.11). Specifically, I intend to revert

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

2016-12-08 Thread Paul Gortmaker
On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: > Hi, > > I'd like to get the GCC plugins building under > allyesconfig/allmodconfig for -next soon (with the intention of > landing the change in v4.11). Specifically, I intend to revert > a519167e753e ("gcc-plugins: disable under COMPILE_TEST").