From: Adrian Bunk <bunk@kernel.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: zippel@linux-m68k.org, sam@ravnborg.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@gmail.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [2.6 patch] HID: fix default building of all quirky devices
Date: Wed, 15 Oct 2008 13:20:56 +0300 [thread overview]
Message-ID: <20081015102056.GH20183@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <alpine.LNX.1.10.0810150931350.26779@jikos.suse.cz>
On Wed, Oct 15, 2008 at 09:43:18AM +0200, Jiri Kosina wrote:
> On Wed, 15 Oct 2008, Adrian Bunk wrote:
>
> > Commit 9be7bbd54df3c9c393ccd19acc49f90c517d1291
> > (HID: build drivers for all quirky devices by default)
> > was wrong in that it select'ed the drivers, causing
> > build errors like the following with CONFIG_USB_HID=n:
> > <-- snip -->
> >
> > ...
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `bright_probe':
> > drivers/hid/hid-bright.c:38: undefined reference to `usbhid_set_leds'
> > drivers/hid/hid-bright.c:38: undefined reference to `usbhid_set_leds'
> > drivers/built-in.o: In function `dell_probe':
> > drivers/hid/hid-dell.c:41: undefined reference to `usbhid_set_leds'
> > drivers/hid/hid-dell.c:41: undefined reference to `usbhid_set_leds'
> > drivers/built-in.o: In function `lg_probe':
> > drivers/hid/hid-lg.c:252: undefined reference to `usbhid_set_leds'
> > drivers/hid/hid-lg.c:252: more undefined references to `usbhid_set_leds' follow
> > drivers/built-in.o: In function `sony_set_operational':
> > drivers/hid/hid-sony.c:42: undefined reference to `usb_control_msg'
> > drivers/hid/hid-sony.c:42: undefined reference to `usb_control_msg'
> > make[1]: *** [.tmp_vmlinux1] Error 1
>
> Hmm ... I am not really sure, isn't this a bug in Kconfig?
No.
> What we have right now:
>
> - CONFIG_HID selects all the individual quirk-drivers automatically
> - the individual quirk drivers have dependency on CONFIG_USB_HID
>
> Therefore I'd expect when CONFIG_HID is selected and CONFIG_USB_HID
> deselected the individual drivers not to get built (due to their
> dependency on unset option).
Different people have different expectations.
Many kernel developers seem to wrongly assume kconfig was something
trivial and everything that does not work as expected was a bug in
kconfig. But it is not, and there is no magic bullet like changing
how select behaves in some way that will suddenly solve all problems.
> But currently what happens is when I de-select CONFIG_USB_HID in
> menuconfig, the configuration options for individual drivers vanish from
> the menuconfig menu (which is expected, they depend on unset option), but
> after saving .config they are still there. Is this how it is expected to
> behave? (i.e. select having preference over dependency).
Select ignores dependencies on the selected options.
That's the documented behavior.
> Thanks,
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
next prev parent reply other threads:[~2008-10-15 10:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 4:13 usbhid_set_leds problems Adrian Bunk
2008-10-15 5:05 ` Adrian Bunk
2008-10-15 7:13 ` Jiri Kosina
2008-10-15 7:30 ` [2.6 patch] HID: fix default building of all quirky devices Adrian Bunk
2008-10-15 7:43 ` Jiri Kosina
2008-10-15 10:20 ` Adrian Bunk [this message]
2008-10-15 17:09 ` Linus Torvalds
2008-10-15 17:17 ` Linus Torvalds
2008-10-15 17:32 ` Adrian Bunk
2008-10-15 17:43 ` Linus Torvalds
2008-10-15 22:54 ` Jiri Kosina
2008-10-16 8:06 ` select validation (was: Re: [2.6 patch] HID: fix default building of all quirky devices) Geert Uytterhoeven
2008-10-16 18:47 ` Linus Torvalds
2008-10-16 19:31 ` Adrian Bunk
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=20081015102056.GH20183@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sam@ravnborg.org \
--cc=torvalds@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