From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [patch, -git] input: CONFIG_INPUT_APANEL build fix
Date: Wed, 30 Apr 2008 22:20:13 +0200 [thread overview]
Message-ID: <20080430202013.GB14164@elte.hu> (raw)
In-Reply-To: <20080430150021.ZZRA012@mailhub.coreip.homeip.net>
* Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On Wed, Apr 30, 2008 at 08:54:16PM +0200, Ingo Molnar wrote:
> >
> > x86.git testing found this build failure in upstream -git:
> >
> > drivers/built-in.o: In function `apanel_detach_client':
> > apanel.c:(.text+0x3027af): undefined reference to `led_classdev_unregister'
> > drivers/built-in.o: In function `apanel_probe':
> > apanel.c:(.text+0x302ac9): undefined reference to `led_classdev_register'
> >
> > with this config:
> >
> > http://redhat.com/~mingo/misc/config-Wed_Apr_30_20_22_20_CEST_2008.bad
> >
> > this driver has a missing CONFIG_NEW_LEDS dependency.
>
> Thank you Ingo. Isn't this a Kconfig issue though? I know that Roman
> is not willing to fix SELECT to evaluate the whole dependency chain,
> but in this case it is "depens on" that does not evaluate properly...
yes and no. It can be fixed in Kconfig but i'm not going to flame yet
another person about long-existing unfixed infrastructure bugs ;-)
The current (many years old) rule is to fix things up as much as we can
and never expose build errors, because 1) randconfig testing is way too
useful and because 2) users can stumble across that .config combination
as well and get rightfully grumpy at us about breaking their build. Most
of the thousands of drivers are fine - it's those with more complex
Kconfig dependencies that have trouble.
Ingo
next prev parent reply other threads:[~2008-04-30 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 18:54 Ingo Molnar
2008-04-30 19:04 ` Dmitry Torokhov
2008-04-30 20:20 ` Ingo Molnar [this message]
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
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=20080430202013.GB14164@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.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 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®