From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Dirk Gouders <dirk@gouders.net>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
USB list <linux-usb@vger.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Roger Quadros <rogerq@ti.com>
Subject: Re: choice =y selection becomes lost after having multiple entries =m with depends on
Date: Thu, 24 Oct 2013 18:19:32 +0200 [thread overview]
Message-ID: <52694894.8090201@linutronix.de> (raw)
In-Reply-To: <givc0mbs9b.fsf@karga.hank.lab>
On 10/24/2013 05:30 PM, Dirk Gouders wrote:
> Hi Sebastian,
Hi Dirk,
> I was looking at what you described and initially had a hard time to
> reproduce the problem, probably because I tried it after `make
> mrproper'. I am only able to reproduce the problem with an existing
> .config of my running kernel, for example.
>
> Just to make sure that I am correctly trying to reproduce the problem:
> did you already try to do what you described after a `make mrproper' and
> do you then also notice the described problems? If not, could you
> please try that?
What is the purpose behind mrproper?
The key to reproduce it is to have a .config with atleast two items
within a choice statement which also have a "depends on" statement and
those set to =m. If you don't have this after mrproper (with your fresh
.config) then you don't see it.
>
> Thanks,
>
> Dirk
Sebastian
next prev parent reply other threads:[~2013-10-24 16:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 10:51 choice =y selection becomes lost after having multiple entries =m with depends on Sebastian Andrzej Siewior
2013-10-23 11:23 ` Yann E. MORIN
2013-10-23 11:28 ` Sebastian Andrzej Siewior
2013-10-24 15:30 ` Dirk Gouders
2013-10-24 16:19 ` Sebastian Andrzej Siewior [this message]
2013-10-24 16:50 ` Dirk Gouders
2013-10-30 10:00 ` Dirk Gouders
2013-10-30 10:30 ` Daniele Forsi
2013-10-30 10:41 ` Dirk Gouders
2013-10-30 14:26 ` Dirk Gouders
2013-10-31 10:20 ` Sebastian Andrzej Siewior
2013-10-31 21:49 ` Yann E. MORIN
2013-11-01 8:45 ` Dirk Gouders
2013-10-31 23:39 ` [PATCH v3] kconfig/symbol.c: handle choice_values that depend on 'm' symbols Dirk Gouders
2013-11-04 17:27 ` Sebastian Andrzej Siewior
2013-11-04 20:46 ` Yann E. MORIN
2013-11-05 8:45 ` Sebastian Andrzej Siewior
2013-11-05 23:04 ` Yann E. MORIN
2013-11-06 14:43 ` Dirk Gouders
2013-11-06 18:59 ` Yann E. MORIN
2013-11-07 14:02 ` Dirk Gouders
2013-11-07 14:05 ` [PATCH v4] " Dirk Gouders
2013-11-18 18:08 ` Yann E. MORIN
2013-12-20 12:46 ` Sebastian Andrzej Siewior
2014-08-13 15:35 ` Bin Liu
2014-08-14 6:52 ` Dirk Gouders
2014-08-14 13:54 ` Bin Liu
2014-08-15 7:37 ` Dirk Gouders
2014-08-15 7:43 ` Sebastian Andrzej Siewior
2016-03-30 22:08 ` Bin Liu
2016-03-30 22:16 ` Ruslan Bilovol
2016-03-31 7:13 ` Roger Quadros
2016-03-31 9:38 ` Dirk Gouders
2016-03-31 9:53 ` Dirk Gouders
2016-04-20 10:19 ` [RESEND PATCH " Dirk Gouders
2016-04-20 11:04 ` kbuild test robot
2016-04-20 13:14 ` Dirk Gouders
2016-04-29 8:24 ` [PATCH v5] " Dirk Gouders
2016-05-02 8:43 ` Roger Quadros
2016-05-10 19:15 ` Michal Marek
2016-04-20 12:12 ` [RESEND PATCH v4] " kbuild test robot
2013-11-08 9:46 ` [PATCH v3] " Dirk Gouders
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=52694894.8090201@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rogerq@ti.com \
--cc=tomi.valkeinen@ti.com \
--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 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).