public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Gao Yunpeng <yunpeng.gao@intel.com>,
	gregkh@suse.de
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 29 (staging/spectra)
Date: Tue, 29 Jun 2010 08:07:57 -0700	[thread overview]
Message-ID: <20100629080757.a8028091.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100629151938.6981044d.sfr@canb.auug.org.au>

On Tue, 29 Jun 2010 15:19:38 +1000 Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20100628:
> 
> My fixes tree is now empty.


When CONFIG_MTD=m and
CONFIG_SPECTRA=y
# CONFIG_SPECTRA_MRST_HW is not set
CONFIG_SPECTRA_MTD=y
# CONFIG_SPECTRA_EMU is not set

build-r3554.out:(.text+0x28bc7c): undefined reference to `put_mtd_device'
build-r3554.out:(.text+0x28bcb1): undefined reference to `get_mtd_device'

due to this in spectra/Kconfig:

config SPECTRA_MTD
	bool "Linux MTD mode"
	depends on MTD

so when CONFIG_MTD=m, the "depends on MTD" on a 'bool' makes the bool become 'y',
which is not good.

Is this supposed to build a separate lld_mtd driver?
Can't it be tristate instead of bool?



---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      parent reply	other threads:[~2010-06-29 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29  5:19 linux-next: Tree for June 29 Stephen Rothwell
2010-06-29 15:02 ` linux-next: Tree for June 29 (hwmon/coretemp) Randy Dunlap
2010-06-29 19:05   ` [lm-sensors] " Jean Delvare
2010-06-29 19:38     ` Jean Delvare
2010-06-29 15:07 ` Randy Dunlap [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=20100629080757.a8028091.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yunpeng.gao@intel.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