From: Marcel Holtmann <marcel@holtmann.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
Jiri Kosina <jkosina@suse.cz>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] HID patches for 2.6.19
Date: Fri, 08 Dec 2006 20:38:17 +0100 [thread overview]
Message-ID: <1165606697.400.2.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0612081126420.3516@woody.osdl.org>
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
next prev parent reply other threads:[~2006-12-08 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 18:54 [GIT PATCH] HID patches for 2.6.19 Greg KH
2006-12-08 19:28 ` Linus Torvalds
2006-12-08 19:38 ` Marcel Holtmann [this message]
2006-12-08 21:34 ` Jiri Kosina
2006-12-08 21:12 ` Greg KH
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=1165606697.400.2.camel@localhost \
--to=marcel@holtmann.org \
--cc=akpm@osdl.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@osdl.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