From: Michal Marek <mmarek@suse.com>
To: Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Emese Revfy <re.emese@gmail.com>,
tautschn@amazon.co.uk, Wolfram Sang <wsa@the-dreams.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] kbuild changes for v4.8-rc1
Date: Tue, 2 Aug 2016 22:59:05 +0200 [thread overview]
Message-ID: <57A10999.9020009@suse.com> (raw)
In-Reply-To: <CAGXu5jK3Hy5eXL20uNCuJ8WNmChWoXictM74_n3Px=N1uki-cw@mail.gmail.com>
Dne 2.8.2016 v 22:55 Kees Cook napsal(a):
> On Tue, Aug 2, 2016 at 1:41 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Tue, Aug 2, 2016 at 3:00 PM, Michal Marek <mmarek@suse.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
next prev parent reply other threads:[~2016-08-02 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 19:00 [GIT PULL] kbuild changes for v4.8-rc1 Michal Marek
2016-08-02 20:41 ` Linus Torvalds
2016-08-02 20:55 ` Kees Cook
2016-08-02 20:59 ` Michal Marek [this message]
2016-08-02 21:00 ` Linus Torvalds
2016-08-02 22:11 ` 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=57A10999.9020009@suse.com \
--to=mmarek@suse.com \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.com \
--cc=tautschn@amazon.co.uk \
--cc=torvalds@linux-foundation.org \
--cc=wsa@the-dreams.de \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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