linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the final tree (mtd tree related)
Date: Tue, 26 Oct 2010 10:15:39 +0100	[thread overview]
Message-ID: <1288084539.29264.15.camel@macbook.infradead.org> (raw)
In-Reply-To: <20101026134959.86b807d1.sfr@canb.auug.org.au>

On Tue, 2010-10-26 at 13:49 +1100, Stephen Rothwell wrote:
> 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"

432dc821c90114f9b0e00f6752a700e937516ade is the first bad commit
commit 432dc821c90114f9b0e00f6752a700e937516ade
Author: H Hartley Sweeten <hartleys@visionengravers.com>
Date:   Thu Aug 19 18:18:21 2010 -0700

    mtd: cleanup Kconfig dependencies

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

      parent reply	other threads:[~2010-10-26  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  2:49 linux-next: build warnings after merge of the final tree (mtd tree related) Stephen Rothwell
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 [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=1288084539.29264.15.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).