[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57A10999.9020009@suse.com>
Date: Tue, 2 Aug 2016 22:59:05 +0200
From: Michal Marek <mmarek@...e.com>
To: Kees Cook <keescook@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Arnd Bergmann <arnd@...db.de>, Emese Revfy <re.emese@...il.com>,
tautschn@...zon.co.uk, Wolfram Sang <wsa@...-dreams.de>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kbuild changes for v4.8-rc1
Dne 2.8.2016 v 22:55 Kees Cook napsal(a):
> On Tue, Aug 2, 2016 at 1:41 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>> On Tue, Aug 2, 2016 at 3:00 PM, Michal Marek <mmarek@...e.com> wrote:
>>>
>>> please merge these kbuild changes for v4.8-rc1:
>>
>> Merged. However, there were two slightly different versions of this
>> commit in my tree:
>>
>>> Kees Cook (2):
>>> kbuild: Abort build on bad stack protector flag
>>
>> differing by $ARCH vs $SRCARCH. There were a few other changes in that
>> area too, so I'd really like you to verify the end result.
>
> The version with $SRCARCH is the correct version. (I think akpm may
> have picked up the v1, but Michal requested some changes that resulted
> in the v2 with the $SRCARCH correction.)
Right, it should be $SRCARCH. But if you accidentally pushed the wrong
version, sky is not going to fall. It's just that make
ARCH=(i386|x86_64|um) will not do the compiler check, until a fix patch
is merged.
Michal
Powered by blists - more mailing lists