From: Greg KH <greg@kroah.com>
To: Peter <cogweb@cogweb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-ac4 build problem
Date: Wed, 4 Sep 2002 23:58:25 -0700 [thread overview]
Message-ID: <20020905065825.GA10140@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209042038490.13193-100000@greenie.frogspace.net>
On Wed, Sep 04, 2002 at 08:59:55PM -0700, Peter wrote:
>
> > Hm, I think you will have to compile the input stuff into the core, if
> > you want your USB input drivers to link properly. So there's really no
> > way around this.
>
> In that case, why don't we remove the choice to make modules in input core
> support?
No, because it works just fine when you build the USB drivers as
modules, and the Input core as modules, which is what the majority of
people do.
> If there's some reason to keep it, let's save someone some grief and add a
> note to CONFIG_INPUT:
>
> Note that in most cases, input support must be compiled into the core for
> your USB input drivers to link properly.
Again, not true. It just has to match the same value for the USB input
drivers. A patch with this kind of wording would be greatly
appreciated.
thanks,
greg k-h
next prev parent reply other threads:[~2002-09-05 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 5:50 2.4.19-ac4 build problem Peter
2002-09-04 16:21 ` Greg KH
2002-09-05 3:59 ` Peter
2002-09-05 6:58 ` Greg KH [this message]
2002-09-12 2:41 ` 2.4.19-ac4 Out of Memory cogwepeter
2003-01-10 2:35 ` 2.4.19 -- ac97_codec failure ALi 5451 Peter
2003-01-10 2:50 ` Alan Cox
2003-01-10 4:30 ` Peter
2003-01-10 13:15 ` Peter
2003-01-10 13:36 ` Alan Cox
2003-01-21 0:41 ` 2.4.20 USB storage (SCSI emulation) Peter Nome
2003-01-21 1:18 ` Matthew Dharm
2003-01-21 2:01 ` Peter Nome
2002-09-05 8:00 ` 2.4.19-ac4 build problem Peter
2002-09-05 16:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-09-04 20:19 Peter
2002-09-04 21:26 ` 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=20020905065825.GA10140@kroah.com \
--to=greg@kroah.com \
--cc=cogweb@cogweb.net \
--cc=linux-kernel@vger.kernel.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