From: Greg KH <greg@kroah.com>
To: Samuel Flory <sflory@rackable.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre10 compile failure USB HID
Date: Fri, 1 Aug 2003 12:44:06 -0700 [thread overview]
Message-ID: <20030801194406.GA31510@kroah.com> (raw)
In-Reply-To: <3F2AC00C.1010203@rackable.com>
On Fri, Aug 01, 2003 at 12:31:24PM -0700, Samuel Flory wrote:
> I'm seeing a linking issue when I compile USB HID support directly
> into the kernel. Looking at my kernel config it looks like it might
> have something to do with the fact that I'm compiling CONFIG_INPUT,
> CONFIG_INPUT_KEYBDEV, and CONFIG_INPUT_MOUSEDEV as modules. Should
> CONFIG_USB_HID depend on one, or all of the above.
Yes, that configuration will not work. I think this has been discussed
many times on the lists in the past, and the end agreement is, "Don't
try to do that." :)
It's not an easy configuration language fix from what I remember.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-01 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 19:31 2.4.22-pre10 compile failure USB HID Samuel Flory
2003-08-01 19:44 ` Greg KH [this message]
2003-08-01 19:47 ` Samuel Flory
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=20030801194406.GA31510@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=sflory@rackable.com \
/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