From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <ak@linux.intel.com>,
andrej.skvortzov@gmail.com, arnaud.patard@rtp-net.org,
Borislav Petkov <bp@suse.de>,
dmitry.kalinkin@gmail.com,
Florian Fainelli <f.fainelli@gmail.com>,
fabio.estevam@freescale.com, Jim Davis <jim.epost@gmail.com>,
riku.voipio@linaro.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [GIT PULL] kbuild misc fixes for v4.2-rc1
Date: Fri, 03 Jul 2015 12:50:50 +0200 [thread overview]
Message-ID: <5596690A.9090004@suse.cz> (raw)
In-Reply-To: <CA+55aFx2NScXTnv_0gx=WBe1RGdzHp=QKkaoh1cpcTZ1HKaSxg@mail.gmail.com>
On 2015-07-03 00:25, Linus Torvalds wrote:
> So with all these changes to the build system fro 4.2, I'm *still*
> getting that annoying
>
> X.509 certificate list changed
>
> issue. Which apparently people don't normally see, because it does to
> stdout rather than to stderr, so it's hidden by all the other random
> build output.
There is a fix for that in in David Howels's tree, the topmost commit being
commit 9c71c950793b1b8c23c6d945b31f6545f82adced
Author: David Woodhouse <David.Woodhouse@intel.com>
Date: Thu May 21 12:23:55 2015 +0100
modsign: Add explicit CONFIG_SYSTEM_TRUSTED_KEYS option
I though it was meant for 4.2, but I do not even see it in linux-next.
David, what's your plan with the patches by David W?
Anyway, none of the kbuild branches was *meant* to fix the issue.
Thanks,
Michal
next prev parent reply other threads:[~2015-07-03 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 20:37 [GIT PULL] kbuild misc fixes for v4.2-rc1 Michal Marek
2015-07-02 22:25 ` Linus Torvalds
2015-07-03 10:50 ` Michal Marek [this message]
2015-07-14 19:42 ` Florian Fainelli
2015-08-27 22:16 ` Florian Fainelli
2015-08-28 8:03 ` Michal Marek
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=5596690A.9090004@suse.cz \
--to=mmarek@suse.cz \
--cc=ak@linux.intel.com \
--cc=andrej.skvortzov@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=bp@suse.de \
--cc=dhowells@redhat.com \
--cc=dmitry.kalinkin@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=jim.epost@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).