public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: linux-usb-devel@lists.sourceforge.net,
	f5ibh <f5ibh@db0bm.ampr.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] USB Config fix for 2.2.19-pre7
Date: Thu, 11 Jan 2001 23:26:32 -0800	[thread overview]
Message-ID: <20010111232632.A19723@kroah.com> (raw)
In-Reply-To: <20010110002639.B26680@wirex.com> <20010110164451.A16985@kroah.com> <5.0.2.1.2.20010111175414.03377210@mail.lauterbach.com>
In-Reply-To: <5.0.2.1.2.20010111175414.03377210@mail.lauterbach.com>; from Franz.Sirl-kernel@lauterbach.com on Thu, Jan 11, 2001 at 06:01:19PM +0100

On Thu, Jan 11, 2001 at 06:01:19PM +0100, Franz Sirl wrote:
> Why do the input handlers depend on CONFIG_USB_HID? On PPC we already have 
> trouble with them depending on CONFIG_USB, so everybody has to select 
> CONFIG_USB even if he just has ADB hardware.

Don't these input drivers _require_ the USB HID driver core to work
properly?  

Or am I mistaken, and this is the 2.4.0 input core code, but
not in a separate directory, like 2.4.0 has it?

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-12  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 20:46 usb mouse, iomega zip and 2.2.19-pre7 f5ibh
2001-01-10  8:26 ` Greg KH
2001-01-11  0:44   ` [PATCH] USB Config fix for 2.2.19-pre7 Greg KH
2001-01-11 17:01   ` [linux-usb-devel] " Franz Sirl
2001-01-12  7:26     ` Greg KH [this message]
2001-01-12 11:57     ` Franz Sirl

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=20010111232632.A19723@kroah.com \
    --to=greg@kroah.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=f5ibh@db0bm.ampr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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