From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Artem.Bityutskiy@nokia.com
Cc: ext Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: linux-next: build failure after merge of the final tree (ubi tree related)
Date: Wed, 16 Mar 2011 21:15:08 +1100 [thread overview]
Message-ID: <1300270508.22236.1168.camel@pasglop> (raw)
In-Reply-To: <1300260170.2817.4.camel@localhost>
On Wed, 2011-03-16 at 09:22 +0200, Artem Bityutskiy wrote:
> On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
> > drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
> > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
> > drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
> >
> > Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
> >
> > I don't know how to fix this, so I have left it for today.
>
> Hmm, strange, include <linux/vmalloc.h> should be enough to use
> __vmalloc with 'PAGE_KERNEL' AFAICS, and we have this include... I'll
> try to look better.
Try adding asm/pgtable.h
Cheers,
Ben.
next prev parent reply other threads:[~2011-03-16 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 6:50 linux-next: build failure after merge of the final tree (ubi tree related) Stephen Rothwell
2011-03-16 7:22 ` Artem Bityutskiy
2011-03-16 10:15 ` Benjamin Herrenschmidt [this message]
2011-03-16 10:27 ` Artem Bityutskiy
2011-03-16 11:48 ` Artem Bityutskiy
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=1300270508.22236.1168.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Artem.Bityutskiy@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).