All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Ingo, no more kconfig patches
Date: Sun, 04 May 2008 00:13:29 +0200	[thread overview]
Message-ID: <m3wsmb6np2.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080503214750.GU5838@cs181133002.pp.htv.fi> (Adrian Bunk's message of "Sun\, 4 May 2008 00\:47\:50 +0300")

Adrian Bunk <bunk@kernel.org> writes:

> If you select LEDS_CLASS "select follows dependencies" would let inherit 
> X86_RDC321X the dependencies of LEDS_CLASS,

I see, "follows" the other way around. That fixes the breakage but I
guess it's not exactly what the people doing make menuconfig want.
Though in absence of the following it would IMHO make sense anyway.

> And regarding "displaying all relevant dependency chains" to the user - 
> I can't see how that would work in the more complicated cases.

I fear it too but perhaps there is some sane way? I don't know,
asking (recursively?) interactively?

Like:
QWERTY requires at least one, select (Y/M):
- ARCH_X86 && NET_ETHERNET, or
- USB4_0 && !SMP, or
- XXX

then:
NET_ETHERNET requires at lest one, select (Y/M):
- PCI128
- ISA256

then (info):
PCI128 requires PCI and it's selected automatically.

I don't know. It could be useful even with a single dependency when
configuring as the module, the user could select Y or M for dependency
interactively (people may want to have E1000E=m and TULIP=m but MII=y).

Not sure if still on the same planet, though :-)
-- 
Krzysztof Halasa

  reply	other threads:[~2008-05-03 22:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:03 [patch] input: JOYSTICK_XPAD build fix Ingo Molnar
2008-04-30 21:02 ` Dmitry Torokhov
2008-04-30 21:13   ` Ingo Molnar
2008-04-30 23:01     ` Ingo, no more kconfig patches Adrian Bunk
2008-05-01  1:17       ` Ingo Molnar
2008-05-01  1:37         ` Adrian Bunk
2008-05-01  2:06           ` Ingo Molnar
2008-05-01  2:12             ` Adrian Bunk
2008-05-01  2:52       ` Ingo Molnar
2008-05-01 11:59         ` Adrian Bunk
2008-05-03 19:14           ` Ingo Molnar
2008-05-03 19:17             ` Ingo Molnar
2008-05-03 20:24             ` Adrian Bunk
2008-05-03 21:03               ` Ingo Molnar
2008-05-03 21:24                 ` Adrian Bunk
2008-05-03 21:38                   ` Sam Ravnborg
2008-05-03 22:07                     ` Adrian Bunk
2008-05-04  7:36                       ` Sam Ravnborg
2008-05-04  7:49                         ` Adrian Bunk
2008-05-03 21:52                   ` Ingo Molnar
2008-05-03 22:03                     ` Adrian Bunk
2008-05-04  3:54                       ` Valdis.Kletnieks
2008-05-04  7:47                         ` Adrian Bunk
2008-05-03 23:22                   ` Thomas Gleixner
2008-05-04  0:34                     ` Adrian Bunk
2008-05-03 21:17               ` Krzysztof Halasa
2008-05-03 21:47                 ` Adrian Bunk
2008-05-03 22:13                   ` Krzysztof Halasa [this message]
2008-05-03 22:29                     ` Adrian Bunk
2008-05-03 23:37                       ` Krzysztof Halasa
2008-05-04  0:49                         ` Adrian Bunk
2008-05-04 12:18                           ` Krzysztof Halasa

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=m3wsmb6np2.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.