From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-cris-kernel@axis.com,
uclinux-dist-devel@blackfin.uclinux.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Build regressions/improvements in v3.9-rc8
Date: Tue, 23 Apr 2013 13:47:32 -0700 [thread overview]
Message-ID: <5176F364.1080101@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1304232132050.11155@ayla.of.borg>
On 04/23/13 12:35, Geert Uytterhoeven wrote:
> + error: "vm_iomap_memory" [drivers/video/fb.ko] undefined!: => N/A
>
> bfin/BF537-STAMP_defconfig
This is a result of the recent iomap changes (I think).
Can Blackfin and others handle a change to FB that says:
depends on MMU
??
then generic fb.o will not be built for no-MMU architectures.
--
~Randy
next prev parent reply other threads:[~2013-04-23 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 19:32 Build regressions/improvements in v3.9-rc8 Geert Uytterhoeven
2013-04-23 19:35 ` Geert Uytterhoeven
2013-04-23 20:47 ` Randy Dunlap [this message]
2013-04-23 21:31 ` Linus Torvalds
2013-04-24 15:38 ` Paul Moore
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=5176F364.1080101@infradead.org \
--to=rdunlap@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=x86@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