From: Michal Marek <mmarek@suse.cz>
To: sedat.dilek@gmail.com, "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 26
Date: Fri, 26 Apr 2013 13:08:35 +0200 [thread overview]
Message-ID: <517A6033.5060103@suse.cz> (raw)
In-Reply-To: <CA+icZUXSsqN1iE3ttQakvpZqG-oOL9NR6RMUezB7LGeUw3d00Q@mail.gmail.com>
On 26.4.2013 12:49, Sedat Dilek wrote:
> On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>> On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek <mmarek@suse.cz> wrote:
>>>> On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote:
>>>>> Can you send a copy of your .config?
>>>>
>>>> I can reproduce it as well:
>>>>
>>>> $ yes "" | make oldconfig
>>>> ...
>>>> Enumeration method [M/y/?] (NEW)
>>>> Basic (RAPIDIO_ENUM_BASIC) [N/m/?] n
>>>> ...
>>>> #
>>>> # configuration written to .config
>>>> #
>>>> $ make oldconfig
>>>> ...
>>>> Enumeration method [M/y/?] (NEW)
>>>>
>>>>
>>>> .config is attached.
>>>>
>>>
>>> Mine, too.
>>>
>>> I hoped that -next release will be one w/o troubles
>>> (cpufreq/intel_pstate / pm/timekeeping / ipc-sem-from-mmotm).
>>> Unfortunately, I am not lucky :-(.
>>>
>>> Anyway, waiting for a fix.
>>>
>>
>> Just FYI: Mail delivery troubles!
>>
>> Delivery to the following recipient failed permanently:
>>
>> yann.morin.1998@free.fr
>>
>> Technical details of permanent failure:
>> Google tried to deliver your message, but it was rejected by the
>> server for the recipient domain free.fr by mx1.free.fr. [212.27.48.6].
>>
>> The error that the other server returned was:
>> 550 spam detected
>> ...
>>
>
> 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 </dev/null
This resulted in
7ded2624f8988bd22819a60a6000ba6b7091db89 is the first bad commit
commit 7ded2624f8988bd22819a60a6000ba6b7091db89
Author: Yann E. MORIN <yann.morin.1998@free.fr>
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?
Thanks,
Michal
next prev parent reply other threads:[~2013-04-26 11:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 8:03 linux-next: Tree for Apr 26 Stephen Rothwell
2013-04-26 8:03 ` Stephen Rothwell
2013-04-26 9:42 ` Sedat Dilek
2013-04-26 9:45 ` Sedat Dilek
2013-04-26 9:58 ` Michal Marek
2013-04-26 10:04 ` Michal Marek
2013-04-26 10:35 ` Sedat Dilek
2013-04-26 10:37 ` Sedat Dilek
2013-04-26 10:49 ` Sedat Dilek
2013-04-26 11:08 ` Michal Marek [this message]
2013-04-26 11:13 ` Michal Marek
2013-04-26 11:23 ` Sedat Dilek
2013-04-26 11:45 ` Sedat Dilek
2013-04-26 11:55 ` Michal Marek
2013-04-26 22:01 ` Yann E. MORIN
2013-04-27 6:54 ` Michal Marek
2013-04-27 11:30 ` Sedat Dilek
2013-04-27 15:24 ` Yann E. MORIN
2013-04-27 15:18 ` Yann E. MORIN
2013-04-26 12:06 ` Yann E. MORIN
2013-04-26 17:34 ` linux-next: Tree for Apr 26 (nfc) Randy Dunlap
2013-04-26 17:59 ` Marcel Holtmann
[not found] ` <20130426180357.7599d1b6b7965470905dcdf3-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2013-04-27 17:06 ` linux-next: Tree for Apr 26 Geert Uytterhoeven
2013-04-27 17:06 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWQ0rMuoH+peGMZ3=AdsYrMPpeV4_vSsLD3kaJukx=83w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-28 23:36 ` Stephen Rothwell
2013-04-28 23:36 ` Stephen Rothwell
[not found] ` <20130429093628.b739ef3b879b6f8759bd31af-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2013-04-29 6:58 ` Geert Uytterhoeven
2013-04-29 6:58 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXZrjaSmttoGHqWCpTkUaxNm3zpWCeU8Lojnp3i=TjhZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 7:08 ` Sedat Dilek
2013-04-29 7:08 ` Sedat Dilek
2013-04-29 8:11 ` Matt Fleming
2013-04-29 8:11 ` Matt Fleming
2013-04-29 8:53 ` Stephen Rothwell
2013-04-29 13:50 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2016-04-26 7:21 Stephen Rothwell
2017-04-26 8:03 Stephen Rothwell
2018-04-26 5:18 Stephen Rothwell
2019-04-26 9:40 Stephen Rothwell
2021-04-26 6:41 Stephen Rothwell
2022-04-26 9:54 Stephen Rothwell
2023-04-26 16:32 broonie
2024-04-26 7:18 Stephen Rothwell
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=517A6033.5060103@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.