From: Scott Wood <scottwood@freescale.com>
To: subrata@linux.vnet.ibm.com
Cc: Jim Cromie <jim.cromie@gmail.com>,
carolyn.j.smith@exgate.tek.com, Adrian Bunk <bunk@kernel.org>,
sachinp <sachinp@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
linux-next <linux-next@vger.kernel.org>,
Alexander Beregalov <a.beregalov@gmail.com>
Subject: Re: [BUILD FAILURE 10/12] Next April 21 : PPC64 randconfig [drivers/mtd/maps/sbc8240.o]
Date: Tue, 21 Apr 2009 15:00:24 -0500 [thread overview]
Message-ID: <49EE25D8.6040906@freescale.com> (raw)
In-Reply-To: <1240340059.9110.143.camel@subratamodak.linux.ibm.com>
Subrata Modak wrote:
> This is a very old one. Doesn´t seem to go away. Reported this earlier
> on 14th April:
> http://lkml.org/lkml/2009/4/14/483,
>
> CC [M] drivers/mtd/maps/sbc8240.o
> drivers/mtd/maps/sbc8240.c:31:1: warning: "DEBUG" redefined
> In file included from drivers/mtd/maps/sbc8240.c:23:
> include/linux/mtd/mtd.h:339:1: warning: this is the location of the
> previous definition
> drivers/mtd/maps/sbc8240.c: In function ‘init_sbc8240_mtd’:
> drivers/mtd/maps/sbc8240.c:172: error: ‘sbc8240_mtd’ undeclared (first
> use in this function)
> drivers/mtd/maps/sbc8240.c:172: error: (Each undeclared identifier is
> reported only once
> drivers/mtd/maps/sbc8240.c:172: error: for each function it appears in.)
> drivers/mtd/maps/sbc8240.c: In function ‘cleanup_sbc8240_mtd’:
> drivers/mtd/maps/sbc8240.c:233: error: ‘sbc8240_mtd’ undeclared (first
> use in this function)
This looks like an arch/ppc orphan. It's not enabled by any defconfig,
and it doesn't look like it does anything that physmap_of can't do.
I'd just remove it.
-Scott
prev parent reply other threads:[~2009-04-21 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 18:54 [BUILD FAILURE 10/12] Next April 21 : PPC64 randconfig [drivers/mtd/maps/sbc8240.o] Subrata Modak
2009-04-21 20:00 ` Scott Wood [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=49EE25D8.6040906@freescale.com \
--to=scottwood@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=a.beregalov@gmail.com \
--cc=bunk@kernel.org \
--cc=carolyn.j.smith@exgate.tek.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).