[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080430224701.GC2629@anvil.corenet.prv>
Date: Wed, 30 Apr 2008 18:47:01 -0400
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Stephen Hemminger <shemminger@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Zippel <zippel@...ux-m68k.org>,
Jan Engelhardt <jengelh@....de>,
Richard Purdie <rpurdie@...ys.net>,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: [patch, -git] input: CONFIG_INPUT_APANEL build fix
On Thu, May 01, 2008 at 12:38:29AM +0200, Ingo Molnar wrote:
>
> * Dmitry Torokhov <dmitry.torokhov@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists