[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1328699901-19488-1-git-send-email-coelho@ti.com>
Date: Wed, 8 Feb 2012 13:18:21 +0200
From: Luciano Coelho <coelho@...com>
To: linux-i2c@...r.kernel.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: tony@...mide.com, khali@...ux-fr.org, ben-linux@...ff.org,
w.sang@...gutronix.de, grant.likely@...retlab.ca,
rob.herring@...xeda.com, devicetree-discuss@...ts.ozlabs.org,
Benoit Cousson <b-cousson@...com>
Subject: [PATCH 3.3 v2] I2C: OMAP: fix build breakage when CONFIG_OF is not set
Since commit 6145197 (i2c: OMAP: Add DT support for i2c controller),
building i2c_omap.c breaks if CONFIG_OF is not set:
drivers/i2c/busses/i2c-omap.c: In function 'omap_i2c_probe':
drivers/i2c/busses/i2c-omap.c:1021: error: 'omap_i2c_of_match' undeclared (first use in this function)
drivers/i2c/busses/i2c-omap.c:1021: error: (Each undeclared identifier is reported only once
drivers/i2c/busses/i2c-omap.c:1021: error: for each function it appears in.)
This is because the definition of omap_i2c_of_match is #ifdef'd on
CONFIG_OF, but the usage of it is not.
Since the places where omap_ic2_of_match are prepared to get NULL
pointers if CONFIG_OF is not defined, we can simply define it to NULL.
Cc: Benoit Cousson <b-cousson@...com>
Signed-off-by: Luciano Coelho <coelho@...com>
Reviewed-by: Felipe Balbi <balbi@...com>
---
v2: changed the commit log to use abbrev sha and include the commit subject
drivers/i2c/busses/i2c-omap.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index f713eac..fd200eb 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -979,6 +979,8 @@ static const struct of_device_id omap_i2c_of_match[] = {
{ },
};
MODULE_DEVICE_TABLE(of, omap_i2c_of_match);
+#else
+static const struct of_device_id *omap_i2c_of_match = NULL;
#endif
static int __devinit
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists