From: Paul Mundt <lethal@linux-sh.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ondrej Zary <linux@rainbow-software.org>
Subject: Re: linux-next: build failure after merge of the final tree (fbdev tree related)
Date: Wed, 20 Apr 2011 18:22:35 +0900 [thread overview]
Message-ID: <20110420092235.GB15898@linux-sh.org> (raw)
In-Reply-To: <20110420141158.008d61b2.sfr@canb.auug.org.au>
On Wed, Apr 20, 2011 at 02:11:58PM +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/video/s3fb.c: In function 's3_pci_remove':
> drivers/video/s3fb.c:1388: error: 'par' undeclared (first use in this function)
>
> Caused by commit 86c0f043a737 ("s3fb: add DDC support"). Clearly not
> tested with CONFIG_MTRR not set :-(
>
> I have reverted that commit for today.
I thought I had MTRR off in my test build, but it seems not.
Fixed now, thanks for the report!
next prev parent reply other threads:[~2011-04-20 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 4:11 linux-next: build failure after merge of the final tree (fbdev tree related) Stephen Rothwell
2011-04-20 9:22 ` Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 6:32 linux-next: build failure after merge of the final tree Stephen Rothwell
2012-02-16 5:29 ` linux-next: build failure after merge of the final tree (fbdev tree related) Stephen Rothwell
2012-02-16 5:29 ` Stephen Rothwell
2013-10-28 14:23 ` Stephen Rothwell
2013-10-28 14:23 ` Stephen Rothwell
2013-10-28 14:39 ` Michal Simek
2013-10-28 14:39 ` Michal Simek
2013-10-29 8:50 ` Tomi Valkeinen
2013-10-29 8:50 ` Tomi Valkeinen
2013-10-29 8:50 ` Tomi Valkeinen
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=20110420092235.GB15898@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rainbow-software.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.