linux-kernel - Re: RFC: kconfig select warnings bogus?

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]

Message-ID: <a781481a0705221013m45f82054tca9a9a78ea8935d4@mail.gmail.com>
Date:	Tue, 22 May 2007 22:43:16 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Stefan Richter" <stefanr@...6.in-berlin.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Roman Zippel" <zippel@...ux-m68k.org>,
	"Kumar Gala" <galak@...nel.crashing.org>,
	"Simon Horman" <horms@...ge.net.au>,
	"Adrian Bunk" <bunk@...sta.de>, "Sam Ravnborg" <sam@...nborg.org>
Subject: Re: RFC: kconfig select warnings bogus?

On 5/22/07, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> Satyam Sharma wrote:
> > On 5/20/07, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> >> > On 5/20/07, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> >> >> config A
> >> >>         bool-or-tristate "option A"
> >> >>         depends on !PLATFORM_X || HELPER_N_ON_PLATFORM_X
> [...]
> > Umm, if A requires helper code N (which is available only on platform X),
> [And, I assumed, 'A' works without helper 'N' on all platforms except
> 'X'.
> This is a synthetic example which might not have a real-world application.]

Well, it is not relevant / equivalent to any of the four symbols that caused the
warnings that this thread is about, at least.

> > then why/how do we want A to depend on platforms _other_ than X?
>
> The expression means:  'A' can be enabled on all platforms.  Except on
> platform_X, there it can only be enabled if helper_N is built too.
> [...]
> No.  I meant "(X && N_ON_X) || Any_one_platform_other_than_X" above.

Yeah, and as I said, this was totally *not* the problem being discussed /
solved in this thread (and by that patch).
-
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/