Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 5 Sep 2002 02:55:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 5 Sep 2002 02:55:52 -0400 Received: from 12-231-243-94.client.attbi.com ([12.231.243.94]:13584 "HELO kroah.com") by vger.kernel.org with SMTP id ; Thu, 5 Sep 2002 02:55:51 -0400 Date: Wed, 4 Sep 2002 23:58:25 -0700 From: Greg KH To: Peter Cc: linux-kernel@vger.kernel.org Subject: Re: 2.4.19-ac4 build problem Message-ID: <20020905065825.GA10140@kroah.com> References:

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 31 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/