From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Marek Subject: Re: linux-next: Tree for Apr 26 Date: Fri, 26 Apr 2013 13:13:33 +0200 Message-ID: <517A615D.9020400@suse.cz> References: <20130426180357.7599d1b6b7965470905dcdf3@canb.auug.org.au> <517A4FC1.3070605@suse.cz> <20130426100435.GA28733@sepie.suse.cz> <517A6033.5060103@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <517A6033.5060103@suse.cz> Sender: linux-kbuild-owner@vger.kernel.org To: sedat.dilek@gmail.com, "Yann E. MORIN" Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org List-Id: linux-next.vger.kernel.org On 26.4.2013 13:08, Michal Marek wrote: > On 26.4.2013 12:49, Sedat Dilek wrote: >> With reverting all kbuild-next commits I was able to build again. >> >> Revert "kconfig: implement KCONFIG_PROBABILITY for randconfig" >> Revert "kconfig: allow specifying the seed for randconfig" >> Revert "kconfig: fix randomising choice entries in presence of >> KCONFIG_ALLCONFIG" >> Revert "kconfig: do not override symbols already set" >> Revert "kconfig: fix randconfig tristate detection" > > I did the same, then applied all the kconfig commits once more and did a > git bisect with this script: > > #!/bin/sh > > cp config-bad .config > make silentoldconfig > This resulted in > > 7ded2624f8988bd22819a60a6000ba6b7091db89 is the first bad commit > commit 7ded2624f8988bd22819a60a6000ba6b7091db89 > Author: Yann E. MORIN > Date: Sun Mar 10 16:34:10 2013 +0100 > > kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG > > The commit id is different, because it is reverted and applied again. Yann? Commit 422c809 ("kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG") reverts cleanly and reverting it fixes the bug. So there is a plan B. Michal