Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 18 Mar 2003 10:07:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 18 Mar 2003 10:07:03 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:6924 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 18 Mar 2003 10:07:02 -0500 Date: Tue, 18 Mar 2003 07:16:06 -0800 (PST) From: Linus Torvalds To: CaT cc: Roman Zippel , , Kernel Mailing List Subject: Re: Linux 2.5.65 In-Reply-To: <20030318103557.GF504@zip.com.au> 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: 768 Lines: 22 On Tue, 18 Mar 2003, CaT wrote: > > Ahhh. So if I want module support but not use it as a module then I'm > SOL? Well, does it _work_ as a built-in? If it does, just send me a patch for the Kconfig file. A lot of the PCMCIA stuff (16-bit) historically _only_ works as modules, because the old PCMCIA code depended on module unload to do a lot of the cleanups that the regular internal eject handling didn't do. But if that driver works for you built-in, then the Kconfig file itself is simply just wrong. Linus - 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/