mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: warn about complex selects
Date: Tue, 6 May 2008 09:26:14 +0300	[thread overview]
Message-ID: <20080506062614.GG1544@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0805060511220.30555@scrub.home>

On Tue, May 06, 2008 at 05:43:32AM +0200, Roman Zippel wrote:
> Hi,

Hi Roman,

>...
> It's not an impossible problem, but it's not trivial either, so that I 
> haven't spend any time on it and rather would like to spend the energy on 
> fixing the problem properly instead of working around it. And the problem 
> BTW isn't select itself, the problem is that all the Kconfig dependencies 
> have grown and become more complex, so it's becoming increasingly more 
> difficult to maintain and to use them - select was never meant to solve 
> this problem...

what do you consider the best solution?

Can we get it solved in kconfig?

Or should kconfig stay the same and use the pattern we already use
with SSB_POSSIBLE?

Or is there some better solution?

> bye, Roman

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2008-05-06  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04  5:40 Vegard Nossum
2008-05-04  6:28 ` Bernd Eckenfels
2008-05-04  8:21 ` Sam Ravnborg
2008-05-04  8:42   ` Ingo Molnar
2008-05-04  8:56   ` Vegard Nossum
2008-05-04 11:00     ` Vegard Nossum
2008-05-04 11:42       ` Sam Ravnborg
2008-05-04  8:48 ` Ingo Molnar
2008-05-06  3:43 ` Roman Zippel
2008-05-06  6:26   ` Adrian Bunk [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=20080506062614.GG1544@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=vegard.nossum@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

all inboxes | Powered by JetHome®