From: Michal Marek <mmarek@suse.cz>
To: Naohiro Aota <naota@elisp.net>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
"Arnaud Lacombe" <lacombar@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-kbuild@vger.kernel.org, "Sam Ravnborg" <sam@ravnborg.org>,
"Ulf Magnusson" <ulfalizer.lkml@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH -next] kconfig: Don't go out from read config loop when you read new symbol
Date: Thu, 30 Sep 2010 22:02:46 +0200 [thread overview]
Message-ID: <20100930200246.GA25629@sepie.suse.cz> (raw)
In-Reply-To: <87sk0rghne.fsf@elisp.net>
On Fri, Oct 01, 2010 at 04:23:17AM +0900, Naohiro Aota wrote:
> commit 8baefd30b5b0101aa07aa75da44a9eee881eed28 of linux-next replaced
> a `switch()' statement with some `if()' statements, but left `break's
> in the `switch()' statement untouched. This cause read config loop to
> exit and so "make oldconfig" is not much usable (see below).
Good catch, applied.
Michal
prev parent reply other threads:[~2010-09-30 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:23 [PATCH -next] kconfig: Don't go out from read config loop when you read new symbol Naohiro Aota
2010-09-30 20:02 ` Michal Marek [this message]
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=20100930200246.GA25629@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=naota@elisp.net \
--cc=sam@ravnborg.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ulfalizer.lkml@gmail.com \
--cc=zippel@linux-m68k.org \
/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).