From: Stefan Richter Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2] Date: Fri, 01 Sep 2006 19:51:39 +0200 Message-ID: <44F8732B.8080102@s5r6.in-berlin.de> References: <44F5DA00.8050909@s5r6.in-berlin.de> <20060830214356.GO18276@stusta.de> <1157069717.2347.13.camel@shinybook.infradead.org> <20060831174852.18efec7e.rdunlap@xenotime.net> <1157074048.2347.24.camel@shinybook.infradead.org> <20060901134425.GA32440@wohnheim.fh-wedel.de> <44F85267.1000607@s5r6.in-berlin.de> <20060901161920.GB32440@wohnheim.fh-wedel.de> <20060901163403.GC18276@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?ISO-8859-1?Q?J=F6rn_Engel?= , David Woodhouse , "Randy.Dunlap" , Roman Zippel , linux-kernel@vger.kernel.org, Christoph Hellwig , David Howells , linux-fsdevel@vger.kernel.org Return-path: Received: from einhorn.in-berlin.de ([192.109.42.8]:1676 "EHLO einhorn.in-berlin.de") by vger.kernel.org with ESMTP id S1750701AbWIAR4U (ORCPT ); Fri, 1 Sep 2006 13:56:20 -0400 To: Adrian Bunk In-Reply-To: <20060901163403.GC18276@stusta.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Adrian Bunk wrote: > On Fri, Sep 01, 2006 at 06:19:20PM +0200, J=F6rn Engel wrote: [...] >> Assuming that select gets removed in the process, and >> concentrating on oldconfig, would it be enough to have something lik= e >> this in the .config? >>=20 >> # CONFIG_USB_STORAGE has unmet dependencies: CONFIG_SCSI, CONFIG_BLO= CK >>=20 >> Now people looking for usb mass storage can find the option without >> grepping through Kconfig files, but also every single driver for eve= ry >> single disabled subsystem shows up. Might be a bit too much. This comment or similar things are apparently not necessary _within=20 subsystems_, just across subsystems, i.e. where the hierarchy of=20 subdirectories and files does not match the hierarchy of dependencies. > Common use case: > A driver was changed to use FW_LOADER. > The .config for the old kernel contains CONFIG_FW_LOADER=3Dn. > The user runs "make oldconfig" with the old .config in the new kernel= =2E >=20 > How do you plan to handle this reasonably without select? "make oldconfig" could ask questions when it sees need to disable=20 formerly enabled options. In general I think: As long as we talk about the various prefab UIs to manipulate .config=20 (i.e. "make {allyes, allmod, allno, def, g, menu, old, rand, silentold,= =20 update-po-, x, ''}config"), there may be ways to implement modes of=20 operation which do what people expect from 'select' but with 'depends=20 on' alone. To ensure that no user group is discriminated in the process= ,=20 committees could be formed. (<- attempt on irony) It will get difficult to entirely please users who don't use these=20 interfaces to .config. But it seems these users are better off without=20 'select'. --=20 Stefan Richter -=3D=3D=3D=3D=3D-=3D-=3D=3D- =3D--=3D ----=3D http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html