From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warnings after merge of the final tree (mtd tree related)
Date: Tue, 26 Oct 2010 13:49:59 +1100 [thread overview]
Message-ID: <20101026134959.86b807d1.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2553 bytes --]
Hi David,
After merging the final tree, today's linux-next build (powerpc
ppc44x_defconfig) produced these warnings:
In file included from drivers/mtd/mtdchar.c:36:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/chipreg.c:11:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/cfi_probe.c:17:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/cfi_probe.c:18:
include/linux/mtd/cfi.h:75:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
In file included from drivers/mtd/maps/physmap_of.c:21:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/cfi_cmdset_0002.c:36:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/cfi_cmdset_0002.c:38:
include/linux/mtd/cfi.h:75:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
In file included from drivers/mtd/chips/cfi_util.c:23:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/cfi_util.c:24:
include/linux/mtd/cfi.h:75:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
In file included from drivers/mtd/chips/gen_probe.c:11:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/gen_probe.c:12:
include/linux/mtd/cfi.h:75:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
In file included from drivers/mtd/chips/jedec_probe.c:21:
include/linux/mtd/map.h:145:2: warning: #warning "No CONFIG_MTD_MAP_BANK_WIDTH_xx selected. No NOR chip support can work"
In file included from drivers/mtd/chips/jedec_probe.c:22:
include/linux/mtd/cfi.h:75:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
I am not sure where these came from ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-10-26 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 2:49 Stephen Rothwell [this message]
2010-10-26 8:51 ` David Woodhouse
2010-10-26 10:49 ` David Woodhouse
2010-10-26 16:43 ` H Hartley Sweeten
2010-10-26 16:48 ` David Woodhouse
2010-10-26 9:15 ` David Woodhouse
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=20101026134959.86b807d1.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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®