Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754564AbbGBWZQ (ORCPT ); Thu, 2 Jul 2015 18:25:16 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:36132 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754442AbbGBWZI (ORCPT ); Thu, 2 Jul 2015 18:25:08 -0400 MIME-Version: 1.0 In-Reply-To: <20150702203736.GA23499@pobox.suse.cz> References: <20150702203736.GA23499@pobox.suse.cz> Date: Thu, 2 Jul 2015 15:25:07 -0700 X-Google-Sender-Auth: tQyEa-8H0FzwxSYKeDwVs5zR6PU Message-ID: Subject: Re: [GIT PULL] kbuild misc fixes for v4.2-rc1 From: Linus Torvalds To: Michal Marek Cc: Andi Kleen , andrej.skvortzov@gmail.com, arnaud.patard@rtp-net.org, Borislav Petkov , dmitry.kalinkin@gmail.com, Florian Fainelli , fabio.estevam@freescale.com, Jim Davis , riku.voipio@linaro.org, Linux Kbuild mailing list , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1544 Lines: 45 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. Making it show more information gives me X.509 certificate list changed to "signing_key.x509" from "./signing_key.x509" so it's still that "./" issue. This is *trivial* to reproduce for me using git clean -dqfx make oldconfig make -j16 make -j16 where that second "make" invocation will do it. Not only is that "./" wrong, but the whole rule to check equality is bad because the certificate list is still generated the wrong way around, and then randomly deleted without proper rules for it. I sent a patch to do it right (using filechk), but it apparently never got merged? Instead, we continue to have that racy "remove the .x509.list file at a random time" thing. Do I need to fish out my patch and apply it directly? I hate just bypassing the maintainership chain for stupid things like this, but this has been pending for way too long. At least that fixes the re-generation of that file, even if it doesn't fix the problem with the spurious extra ./ at the head. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/