mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "eric miao" <eric.y.miao@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Kumar Gala" <galak@kernel.crashing.org>,
	spi-devel-general@lists.sourceforge.net,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [spi-devel-general] SPI related Kconfig warning
Date: Thu, 31 Jan 2008 17:27:01 +0800	[thread overview]
Message-ID: <f17812d70801310127h64f77b10td33a4736b3a23836@mail.gmail.com> (raw)
In-Reply-To: <200801302321.51120.david-b@pacbell.net>

On Jan 31, 2008 3:21 PM, David Brownell <david-b@pacbell.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

  reply	other threads:[~2008-01-31  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  4:41 Kumar Gala
2008-01-31  7:21 ` [spi-devel-general] " David Brownell
2008-01-31  9:27   ` eric miao [this message]
2008-02-02 20:51 ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f17812d70801310127h64f77b10td33a4736b3a23836@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®