From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ondrej Zary <linux@rainbow-software.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: linux-next: build failure after merge of the i2c tree (arm tree interaction)
Date: Fri, 11 Feb 2011 11:45:14 +1100 [thread overview]
Message-ID: <20110211114514.67f377b9.sfr@canb.auug.org.au> (raw)
Hi Jean,
After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/video/cyber2000fb.c:51:26: error: linux/i2c-id.h: No such file or directory
Caused by commit 06bc0fe05c62297e1db2979d591770459439866e ("i2c: Get rid
of <linux/i2c-id.h>") interacting with commit
8749b1ad69f91be1f5735563c7f235f802c7ea7d ("VIDEO: cyberpro: add I2C
support") from the arm tree.
I applied the following fix up patch for today. Russell, this could be
applied in the arm tree as there is nothing relevant in that header file
even in Linus' tree.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 11 Feb 2011 11:41:35 +1100
Subject: [PATCH] VIDEO: cyberpro: remove obsolate include
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
drivers/video/cyber2000fb.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/video/cyber2000fb.c b/drivers/video/cyber2000fb.c
index 44db875..8503807 100644
--- a/drivers/video/cyber2000fb.c
+++ b/drivers/video/cyber2000fb.c
@@ -48,7 +48,6 @@
#include <linux/init.h>
#include <linux/io.h>
#include <linux/i2c.h>
-#include <linux/i2c-id.h>
#include <linux/i2c-algo-bit.h>
#include <asm/pgtable.h>
--
1.7.2.3
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next reply other threads:[~2011-02-11 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 0:45 Stephen Rothwell [this message]
2011-02-11 8:16 ` linux-next: build failure after merge of the i2c tree (arm tree interaction) Jean Delvare
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=20110211114514.67f377b9.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=rmk@arm.linux.org.uk \
/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