linux-kernel - Re: [RFC v1] tree-wide: remove "select FW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 May 2015 20:25:35 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	"Luis R. Rodriguez" <mcgrof@...e.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Takashi Iwai <tiwai@...e.de>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Borislav Petkov <bp@...en8.de>,
	Greg KH <gregkh@...uxfoundation.org>,
	"David S. Miller" <davem@...emloft.net>, clemens@...isch.de,
	JBottomley@...n.com, David Airlie <airlied@...ux.ie>,
	Mauro Carvalho Chehab <mchehab@....samsung.com>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Marcel Holtmann <marcel@...tmann.org>,
	"Gustavo F. Padovan" <gustavo@...ovan.org>,
	Johan Hedberg <johan.hedberg@...il.com>,
	Mikael Starvik <starvik@...s.com>,
	Jesper Nilsson <jesper.nilsson@...s.com>,
	Imre Kaloz <kaloz@...nwrt.org>, khalasa@...p.pl,
	Ohad Ben-Cohen <ohad@...ery.com>,
	Arnd Bergmann <arnd@...db.de>, 3chas3@...il.com,
	Jiri Slaby <jslaby@...e.cz>, Bryan Wu <cooloney@...il.com>,
	Richard Purdie <rpurdie@...ys.net>,
	Jacek Anaszewski <j.anaszewski@...sung.com>,
	mcgrof@...not-panic.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC v1] tree-wide: remove "select FW_LOADER" uses

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/