Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751282AbbEYSZm (ORCPT ); Mon, 25 May 2015 14:25:42 -0400 Received: from lb3-smtp-cloud3.xs4all.net ([194.109.24.30]:54735 "EHLO lb3-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750894AbbEYSZj (ORCPT ); Mon, 25 May 2015 14:25:39 -0400 Message-ID: <1432578335.27695.186.camel@x220> Subject: Re: [RFC v1] tree-wide: remove "select FW_LOADER" uses From: Paul Bolle To: Josh Triplett Cc: "Luis R. Rodriguez" , Dmitry Torokhov , Takashi Iwai , Geert Uytterhoeven , Borislav Petkov , Greg KH , "David S. Miller" , clemens@ladisch.de, JBottomley@odin.com, David Airlie , Mauro Carvalho Chehab , Herbert Xu , Marcel Holtmann , "Gustavo F. Padovan" , Johan Hedberg , Mikael Starvik , Jesper Nilsson , Imre Kaloz , khalasa@piap.pl, Ohad Ben-Cohen , Arnd Bergmann , 3chas3@gmail.com, Jiri Slaby , Bryan Wu , Richard Purdie , Jacek Anaszewski , mcgrof@do-not-panic.com, "linux-kernel@vger.kernel.org" Date: Mon, 25 May 2015 20:25:35 +0200 In-Reply-To: <20150525175431.GD1037@x> References: <1432282668.27695.24.camel@x220> <20150522175711.GE40101@dtor-ws> <20150522181924.GN23057@wotan.suse.de> <20150522185207.GG40101@dtor-ws> <20150522192814.GO23057@wotan.suse.de> <20150522214357.GA24129@cloud> <1432551316.27695.166.camel@x220> <20150525175431.GD1037@x> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1740 Lines: 42 On Mon, 2015-05-25 at 10:54 -0700, Josh Triplett wrote: > I don't mean cyclic dependencies (for which Kconfig should just report > an error, ideally including the full list of symbols forming the cycle). > > I mean that Kconfig should do recursive dependency resolution. (My English might be letting me down here. Or my grasp of elementary logic, for that matter. Recursive and cyclic are not really interchangeable? Should Kconfig perhaps report a "Cyclic dependency error"? ) > If B > depends on A, and C depends on B, I should be able to turn on C > directly and have B and A enabled. And how should kconfig handle, say: - B depends on (A || D) - C depends on B Should (B && D) be enabled or (B && A)? This is not meant as a rhetorical question. But I do fear the complications for the choices this idea might encounter are, at best, not worth the effort. > As an intermediate measure, it'd be *really* handy to be able to browse > in the curses UI directly from a symbol to the symbols it depends on to > quickly enable/disable them, rather than having to look at the list of > dependencies of a symbol, search for that symbol, remember the path the > search showed, and browse there manually. Probably. I'd rather not think about the UI involved when the symbol(s) that should be enabled is (are) two or more levels down the chain. And the odd "stacked" UI for searches in the curses tool adds to the fun. But then again, I'm a the-glass-is-half-empty person. Paul Bolle -- 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/