Hi Linus,
> > Here are some patches that move the HID code to a new directory allowing
> > it to be used by other kernel subsystems easier.
>
> I pulled. However, I think the Kconfig changes are HORRIBLE.
>
> I don't understand why people don't use "select" more. Why should Kconfig
> ask for "Generic HID support?" That question _never_ makes sense to a
> user. And if you answer "n", you'll not get USB_HID.
>
> This is not user-friendly. If you need HID support, just select it. Don't
> ask people questions that make no sense. If the generic HID code is needed
> for some driver, you just select it. If it's not needed, you don't. It's
> that easy.
since we don't have any user-space or out of kernel HID transport
drivers at the moment it would make sense to simply select HID if
someone selects USB_HID or the upcoming Bluetooth transport.
Regards
Marcel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
