Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Dec 2002 18:54:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Dec 2002 18:54:44 -0500 Received: from air-2.osdl.org ([65.172.181.6]:6537 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Thu, 19 Dec 2002 18:54:42 -0500 Date: Thu, 19 Dec 2002 16:01:32 -0800 (PST) From: "Randy.Dunlap" X-X-Sender: To: Justin Pryzby cc: Subject: Re: Bug? undefined reference to `input_event' In-Reply-To: <20021219234705.GA11106@perseus.homeunix.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 943 Lines: 29 On Thu, 19 Dec 2002, Justin Pryzby wrote: | Is somebody keeping fixing, or at least keeping track of, these | configuration errors? I've seen a bunch of configuration problems, and | the typical response doesn't include a patch (which is fine, as long as | it ultimately gets fixed). If something can't be configured as a module, | then it shouldn't be possible to configure it as a module. That's what the kernel bugzilla is for. http://bugzilla.kernel.org or http://bugme.osdl.org And some of us are trying to address the issues. | I can write patches for these things if someone gives me pointers for | how the 2.{4,5} kernel configuration stuff works. | | > Stuff deleted... -- ~Randy - 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/