From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Roman Zippel <zippel@linux-m68k.org>,
Jan Engelhardt <jengelh@gmx.de>,
Richard Purdie <rpurdie@rpsys.net>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [patch, -git] input: CONFIG_INPUT_APANEL build fix
Date: Wed, 30 Apr 2008 18:47:01 -0400 [thread overview]
Message-ID: <20080430224701.GC2629@anvil.corenet.prv> (raw)
In-Reply-To: <20080430223828.GA31878@elte.hu>
On Thu, May 01, 2008 at 12:38:29AM +0200, Ingo Molnar wrote:
>
> * Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > > i'm not suggesting this is your fault in any way - but nevertheless
> > > many other subsystems have to deal with the same Kconfig issues and
> > > they manage to limp along.
> >
> > I believe I see a steady stream of breakage for leds dependencies from
> > all subsystems.
>
> they limp along by adding "depends on NEW_LEDS". 99% of the users will
> use some pre-cooked distro kernel where all these options are turned on,
> so the flattening and coupling of the dependencies is not a real issue
> in practice.
You still did not answer to the main question - do you think we should
revert the commit that actually introduced breakage in the sense that
anything depending on LEDS_CLASS should also add NEW_LEDS dependancy?
That will take care of the problem (as far as LEDs are concerned) for
_all_ subsystems and drivers at once.
--
Dmitry
next prev parent reply other threads:[~2008-04-30 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 18:54 [patch, -git] input: CONFIG_INPUT_APANEL build fix Ingo Molnar
2008-04-30 19:04 ` Dmitry Torokhov
2008-04-30 20:20 ` Ingo Molnar
2008-04-30 20:56 ` Roman Zippel
2008-04-30 22:21 ` Dmitry Torokhov
2008-04-30 21:00 ` Dmitry Torokhov
2008-04-30 21:20 ` Ingo Molnar
2008-04-30 22:26 ` Dmitry Torokhov
2008-04-30 22:38 ` Ingo Molnar
2008-04-30 22:47 ` Dmitry Torokhov [this message]
2008-05-01 0:51 ` Roman Zippel
2008-05-01 2:36 ` Dmitry Torokhov
2008-05-01 6:25 ` Jan Engelhardt
2008-05-01 1:29 ` Ingo Molnar
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=20080430224701.GC2629@anvil.corenet.prv \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jengelh@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rpurdie@rpsys.net \
--cc=sam@ravnborg.org \
--cc=shemminger@linux-foundation.org \
--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 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.