From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Ball <cjb@laptop.org>
Subject: linux-next: build failure after merge of the final tree (viafb tree related)
Date: Tue, 27 Apr 2010 15:49:25 +1000 [thread overview]
Message-ID: <20100427154925.7315ed67.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Hi Jon,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/video/via/hw.c:21:22: error: asm/olpc.h: No such file or directory
drivers/video/via/lcd.c:21:22: error: asm/olpc.h: No such file or directory
drivers/video/via/hw.c: In function 'init_tmds_chip_info':
drivers/video/via/hw.c:2043: error: implicit declaration of function 'machine_is_olpc'
drivers/video/via/lcd.c: In function 'viafb_lvds_trasmitter_identify':
drivers/video/via/lcd.c:179: error: implicit declaration of function 'machine_is_olpc'
Caused by commit 78af0539da7b8069cb30023a3ec648e353849d3c ("viafb: Do not
probe for LVDS/TMDS on OLPC XO-1.5") from the viafb tree.
I have reverted that commit (and ab73d3d6066b57963ead15f3c1d1a55b16520e14
"viafb: rework the I2C support in the VIA framebuffer driver",
b3af18ed0ed5161801545f40705b9ec50bd9ebb6 "suppress verbose debug
messages: change printk() to DEBUG_MSG()" and
81b7734bd9f0a25e29d9d943e020fa57aee738b4 "viafb: Only establish i2c
busses on ports that always had them" that conflicted with the revert)
for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-04-27 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:49 Stephen Rothwell [this message]
2010-04-27 12:43 ` linux-next: build failure after merge of the final tree (viafb tree related) Jonathan Corbet
2010-04-27 14:12 ` Stephen Rothwell
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=20100427154925.7315ed67.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cjb@laptop.org \
--cc=corbet@lwn.net \
--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