From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for Jun 25
Date: Tue, 25 Jun 2013 11:21:53 +0200 [thread overview]
Message-ID: <201306251121.53862.yann.morin.1998@free.fr> (raw)
In-Reply-To: <CA+icZUUH7AeR7OSm-SB56AGRiE815tTkQW9fFkKzyrSvzs3Etg@mail.gmail.com>
Sedat, All,
On Tuesday 25 June 2013 10:55:20 Sedat Dilek wrote:
> Not sure what's going on, but I get this with today's Linux-Next.
> ( Yesterday's next-20130624 was OK. )
>
> $ LANG=C LC_ALL=C yes "" | make oldconfig && LANG=C LC_ALL=C make
> silentoldconfig </dev/null
[--SNIP--]
> RapidIO support (RAPIDIO) [Y/n/?] y
> IDT Tsi721 PCI Express SRIO Controller support (RAPIDIO_TSI721) [Y/n/?] y
> Discovery timeout duration (seconds) (RAPIDIO_DISC_TIMEOUT) [30] 30
> Enable RapidIO Input/Output Ports (RAPIDIO_ENABLE_RX_TX_PORTS) [N/y/?] n
> DMA Engine support for RapidIO (RAPIDIO_DMA_ENGINE) [Y/n/?] y
> RapidIO subsystem debug messages (RAPIDIO_DEBUG) [N/y/?] n
> Enumeration method [M/y/?] (NEW) aborted!
>
> Console input/output is redirected. Run 'make oldconfig' to update
> configuration.
Yes, the same error as reported by Fengguang earlier:
http://marc.info/?l=linux-kbuild&m=137214773928335&w=4
And caused by (yet once more):
8357b48: kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG
Basically, the issue is:
- 'Enumeration method' is a tristate choice
- for tristate choices, it is possible to select zero, one or more of the
symbols in the choice
- if no symbol is selected (randomly or otherwise) in a tristate choice,
then the choice symbol itself has no assigned 'value'
- then silentoldconfig whines
It worked so far as a side effect of another bug (which 8357b48 tries to
fix), and now this new one has been exposed.
I have to think in a calm place tonight, when I'm back from work...
This one is starting to drive me crazy, really... :-(
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
next prev parent reply other threads:[~2013-06-25 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 8:44 linux-next: Tree for Jun 25 Stephen Rothwell
2013-06-25 8:55 ` Sedat Dilek
2013-06-25 9:21 ` Yann E. MORIN [this message]
2013-06-25 9:26 ` Sedat Dilek
2013-06-25 9:30 ` Michal Marek
2013-06-25 9:40 ` Sedat Dilek
2013-06-25 21:03 ` Yann E. MORIN
2013-06-25 21:27 ` Sedat Dilek
2013-06-25 12:03 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 11:54 Stephen Rothwell
2020-06-25 6:34 Stephen Rothwell
2019-06-25 10:37 Stephen Rothwell
2018-06-25 5:43 Stephen Rothwell
2015-06-25 8:17 Stephen Rothwell
2014-06-25 5:04 Stephen Rothwell
2012-06-25 7:06 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=201306251121.53862.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).