From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sedat Dilek <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 23:03:14 +0200 [thread overview]
Message-ID: <20130625210314.GC14074@free.fr> (raw)
In-Reply-To: <CA+icZUU06C43bxyX2UGtDxRQqcyqeAQgt7fZHq7H7HgcJ6sHzQ@mail.gmail.com>
Sedat, All,
On 2013-06-25 11:26 +0200, Sedat Dilek spake thusly:
> On Tue, Jun 25, 2013 at 11:21 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > 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.
[--SNIP--]
> Bad bad bad Yann, didn't Marek told you to test always with...
>
> $ yes "" | make oldconfig; make silentoldconfig </dev/null
If you looked at the commit log, you'd see how I tested this:
touch defconfig
for(( i=0; i<10000; i++ )); do
KCONFIG_ALLCONFIG=$(pwd)/defconfig make randconfig >/dev/null 2>&1
make silentoldconfig </dev/null >/dev/null 2>&1 || break
done
That is, 10 thousands random configurations, and none did exhibit the
problem. :-(
Which really means we need a comprehensive test-suite to kconfig.
> Anyway, have fun.
I would not call delving into the kconfig code 'fun'. ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-06-25 21:03 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
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 [this message]
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=20130625210314.GC14074@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).