Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 2 Nov 2002 06:46:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 2 Nov 2002 06:46:59 -0500 Received: from smtpzilla3.xs4all.nl ([194.109.127.139]:40460 "EHLO smtpzilla3.xs4all.nl") by vger.kernel.org with ESMTP id ; Sat, 2 Nov 2002 06:46:58 -0500 Date: Sat, 2 Nov 2002 12:53:21 +0100 (CET) From: Roman Zippel X-X-Sender: roman@serv To: "Theodore Ts'o" cc: linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: [PATCH] Fix 2.5-bk build error In-Reply-To: <20021102065444.GA16100@think.thunk.org> Message-ID: References: <20021101002419.GA1683@rivenstone.net> <20021101004751.GB1683@rivenstone.net> <20021101010607.GC1683@rivenstone.net> <20021101172807.GA982@caphernaum.rivenstone.net> <20021102065444.GA16100@think.thunk.org> 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: 1072 Lines: 30 Hi, On Sat, 2 Nov 2002, Theodore Ts'o wrote: > On Fri, Nov 01, 2002 at 12:28:07PM -0500, Joseph Fannin wrote: > > > BTW2 in the future above can be simplified into > > > > > > config FS_MBCACHE > > > tristate > > > depends on EXT2_FS_XATTR || EXT3_FS_XATTR > > > default EXT2_FS || EXT3_FS > > > > Okay, here's a patch that does that. Linus, this fixes a build > > error in your current -bk tree that happens when one of ext[23] is a > > module and the other is built-in. Please apply it. > > Um, Roman, am I right in understanding that when you say, "in the > future above can be simplified" means that infrastructure to support > this construct isn't merged into the 2.5 kernel yet? No, it means that the support for this isn't written yet. I have looked into it, but it's not actually done yet. bye, Roman - 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/