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
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
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
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
[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
[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
*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
*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
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:
>> >
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
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
> >>
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
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
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
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
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
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
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.
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).
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
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
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
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
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
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
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
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
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
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
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").
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").
Right now the plugins are only supported on x86, arm, and
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").
Right now the plugins are only supported on x86, arm, and
32 matches
Mail list logo