linux-kernel - Re: [spi-devel-general] SPI related Kconfig warning

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:	Thu, 31 Jan 2008 17:27:01 +0800
From:	"eric miao" <eric.y.miao@...il.com>
To:	"David Brownell" <david-b@...bell.net>
Cc:	"Kumar Gala" <galak@...nel.crashing.org>,
	spi-devel-general@...ts.sourceforge.net,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [spi-devel-general] SPI related Kconfig warning

On Jan 31, 2008 3:21 PM, David Brownell <david-b@...bell.net> wrote:
> On Wednesday 30 January 2008, Kumar Gala wrote:
> > Was wondering if anyone was looking at the cause of this warning in
> > top of linus's tree (8af03e782cae1e0a0f530ddd22301cdd12cf9dc0)
> >
> > drivers/spi/Kconfig:156:warning: 'select' used by config symbol
> > 'SPI_PXA2XX' refers to undefined symbol 'PXA_SSP'
> >
> > I was doing a build of a ppc kernel.
>
> Happens on x86, AVR32, and non-PXA ARM too.  Came from some PXA cleanup
> patches.  Eric, didn't you have a patch for this?
>

Nope.

If moving the symbol PXA_SSP to the "depends on" list, this option will
remain invisible if a careless user does not select PXA_SSP.

Yet I'm not sure this is the way to go or mandatory by the kconfig rules.

> (Of course I *still* don't understand why kconfig bothers to look
> at reverse dependencies whose "forward" ones can never be satisfied.
> If it stopped looking at those, lots of similar problems would vanish.)
>
> - Dave
>



-- 
Cheers
- eric
--
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/