public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Kconfig undefined references (on other platforms)
Date: Wed, 16 May 2007 08:16:36 -0700	[thread overview]
Message-ID: <20070516151635.GB20297@atomide.com> (raw)
In-Reply-To: <463F80E7.9040201@am.sony.com>

* Tim Bird <tim.bird@am.sony.com> [070507 12:43]:
> Hi all,
> 
> I'm using patch-2.6.20-omap1, with a kernel that I compile
> for multiple boards. When I compile the kernel for a MIPS board,
> I get some Kconfig warnings on OMAP symbols.
> 
> >From the compile:
> scripts/kconfig/conf -s arch/mips/Kconfig
> sound/arm/Kconfig:42:warning: 'select' used by config symbol 'SND_OMAP_AIC23' refer to undefined symbol 'OMAP_MCBSP'
> sound/arm/Kconfig:57:warning: 'select' used by config symbol 'SND_OMAP_TSC2101' refer to undefined symbol 'OMAP_MCBSP'
> sound/arm/Kconfig:70:warning: 'select' used by config symbol 'SND_SX1' refer to undefined symbol 'OMAP_MCBSP'
> 
> It looks like sound/arm/Kconfig is included (unconditionally) in
> sound/Kconfig. OMAP_MCBSP is defined in arch/arm/plat-omap1/Kconfig,
> which is not included during my build on MIPS.
> 
> Does anyone know what the proper technique is for making either the
> selects or the includes conditional, or otherwise quieting these
> types of reference warnings?

Sounds like it would be best to have board-*.c functions take care
of of the mcbsp read/write for omap.

Tony

      reply	other threads:[~2007-05-16 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 19:41 Kconfig undefined references (on other platforms) Tim Bird
2007-05-16 15:16 ` tony [this message]

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=20070516151635.GB20297@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tim.bird@am.sony.com \
    /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