From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: "Shargorodsky Atal (EXT-Teleca/Helsinki)"
<ext-atal.shargorodsky@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] Allow I2C_OMAP to compile as a module.
Date: Fri, 13 Feb 2009 14:21:00 -0800 [thread overview]
Message-ID: <20090213222100.GJ7562@atomide.com> (raw)
In-Reply-To: <20090213085827.d516d6aa.jarkko.nikula@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
* Jarkko Nikula <jarkko.nikula@nokia.com> [090212 22:58]:
> On Thu, 12 Feb 2009 15:10:29 +0100
> "Shargorodsky Atal (EXT-Teleca/Helsinki)"
> <ext-atal.shargorodsky@nokia.com> wrote:
>
> > This patch allows I2C_OMAP to be compiled as a module.
> > Only drivers/i2c/busses/i2c-omap.c can be compiled as a module,
> > but not arch/arm/plat-omap/i2c.c , so let the contents of i2c.c
> > to compile into the kernel if either I2C_OMAP was selected to compile
> > in or as a module.
> >
> > Signed-off-by: Atal Shargorodsky <ext-atal.shargorodsky@nokia.com>
> > ---
> > arch/arm/plat-omap/Makefile | 3 +--
> > arch/arm/plat-omap/i2c.c | 4 ++++
> > 2 files changed, 5 insertions(+), 2 deletions(-)
> >
> Tony,
>
> You can add this to your 2.6.29-rc series since the same build error is
> in mainline as well if CONFIG_I2C_OMAP=m.
>
> Building modules, stage 2.
> GZIP arch/arm/boot/compressed/piggy.gz
> MODPOST 6 modules
> ERROR: "i2c_register_board_info" [arch/arm/plat-omap/i2c.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> make: *** Waiting for unfinished jobs....
>
> Subject needs a "ARM: OMAP: " prefix, otherwise ok from me.
>
> Acked-by: Jarkko Nikula <jarkko.nikula@nokia.com>
Sounds like a fix, except I posted a shorter version of the patch that
should do the trick (untested). Attached here too for reference.
Tony
[-- Attachment #2: i2c-omap-module.patch --]
[-- Type: text/x-diff, Size: 472 bytes --]
--- a/arch/arm/plat-omap/Makefile
+++ b/arch/arm/plat-omap/Makefile
@@ -21,7 +21,10 @@ obj-$(CONFIG_OMAP_COMPONENT_VERSION) += component-version.o
obj-$(CONFIG_OMAP_GPIO_SWITCH) += gpio-switch.o
obj-$(CONFIG_OMAP_DEBUG_DEVICES) += debug-devices.o
obj-$(CONFIG_OMAP_DEBUG_LEDS) += debug-leds.o
-obj-$(CONFIG_I2C_OMAP) += i2c.o
+
+ifneq ($(CONFIG_I2C_OMAP),)
+ obj-$(CONFIG_I2C_OMAP) += i2c.o
+endif
# OMAP mailbox framework
obj-$(CONFIG_OMAP_MBOX_FWK) += mailbox.o
next prev parent reply other threads:[~2009-02-13 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 14:10 [PATCH 1/1] Allow I2C_OMAP to compile as a module Atal Shargorodsky
2009-02-13 6:58 ` Jarkko Nikula
2009-02-13 22:21 ` Tony Lindgren [this message]
2009-02-15 19:35 ` Jarkko Nikula
2009-02-15 19:45 ` Jarkko Nikula
2009-02-16 16:40 ` Aaro Koskinen
2009-02-16 23:09 ` Tony Lindgren
2009-02-17 9:25 ` Jarkko Nikula
2009-02-17 23:50 ` Tony Lindgren
2009-02-17 23:59 ` Otto Solares
2009-02-18 0:07 ` Tony Lindgren
2009-02-18 9:22 ` [PATCH] ARM: OMAP: Allow I2C bus driver to be compiled " Aaro Koskinen
2009-02-18 9:45 ` Jarkko Nikula
2009-02-18 23:40 ` Tony Lindgren
2009-02-18 23:43 ` Otto Solares
2009-02-18 23:59 ` Tony Lindgren
2009-02-19 0:15 ` Otto Solares
2009-02-16 23:09 ` [PATCH 1/1] Allow I2C_OMAP to compile " Tony Lindgren
2009-02-15 20:47 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2009-02-12 12:54 Atal Shargorodsky
2009-02-12 13:10 ` Jarkko Nikula
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=20090213222100.GJ7562@atomide.com \
--to=tony@atomide.com \
--cc=ext-atal.shargorodsky@nokia.com \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@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