From: Ben Hutchings <bhutchings@solarflare.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-net-drivers@solarflare.com
Subject: Re: linux-next: Tree for November 19 (mtd build error)
Date: Wed, 19 Nov 2008 19:18:07 +0000 [thread overview]
Message-ID: <1227122287.3052.7.camel@achroite> (raw)
In-Reply-To: <492463A1.3000306@oracle.com>
On Wed, 2008-11-19 at 11:06 -0800, Randy Dunlap wrote:
> David Woodhouse wrote:
> > On Wed, 2008-11-19 at 10:53 -0800, Randy Dunlap wrote:
> >> On Wed, 19 Nov 2008 17:59:17 +1100 Stephen Rothwell wrote:
> >>
> >> (.text+0x104879): undefined reference to `add_mtd_device'
> >> (.text+0x1048e1): undefined reference to `del_mtd_device'
> >> mtd.c:(.text+0x104999): undefined reference to `mtd_erase_callback'
> >>
> >>
> >> config attached.
> >
> > CONFIG_SFC_MTD=y
> >
> > What's that?
>
> drivers/net/sfc/Kconfig:
>
> config SFC_MTD
> bool "Solarflare Solarstorm SFC4000 flash MTD support"
> depends on SFC && MTD
> default y
> help
> This exposes the on-board flash memory as an MTD device (e.g.
> /dev/mtd1). This makes it possible to upload new boot code
> to the NIC.
>
>
> sfc people added to cc.
Please use the address linux-net-drivers@solarflare.com, as listed in
MAINTAINERS. There are several of us working on the driver, and they
no longer include Michael Brown.
David Woodhouse wrote:
> Sounds like this was built-in while CONFIG_MTD=m
So does the dependency need to be something like
"depends on SFC && MTD && !(SFC=y && MTD=m)"?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-11-19 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 6:59 linux-next: Tree for November 19 Stephen Rothwell
2008-11-19 18:48 ` linux-next: Tree for November 19 (staging/go7007/) Randy Dunlap
2008-11-19 19:08 ` Greg KH
2008-11-19 18:51 ` linux-next: Tree for November 19 (v4l2 warnings) Randy Dunlap
2008-11-20 0:02 ` Stephen Rothwell
2008-11-20 11:11 ` Mauro Carvalho Chehab
2008-11-19 18:53 ` linux-next: Tree for November 19 (mtd build error) Randy Dunlap
2008-11-19 18:58 ` David Woodhouse
2008-11-19 19:06 ` Randy Dunlap
2008-11-19 19:08 ` David Woodhouse
2008-11-19 19:18 ` Ben Hutchings [this message]
2008-11-19 19:24 ` David Woodhouse
2008-11-19 19:43 ` Ben Hutchings
2008-11-19 19:45 ` Randy Dunlap
2008-11-19 18:55 ` linux-next: Tree for November 19 (dvb build errors) Randy Dunlap
2008-11-19 18:59 ` linux-next: Tree for November 19 (ipw2100/2200 " Randy Dunlap
2008-11-19 19:15 ` [PATCH] coda: fix creds reference Randy Dunlap
2008-11-19 19:33 ` [PATCH -next resend] nfsctl: add headers for credentials Randy Dunlap
2008-11-19 21:17 ` linux-next: Tree for November 19 (section mismatche fpu_init) Richard Holden
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=1227122287.3052.7.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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