From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Aaro Koskinen <Aaro.Koskinen@nokia.com>,
linux-omap@vger.kernel.org, jarkko.nikula@nokia.com,
ext-atal.shargorodsky@nokia.com
Subject: Re: [PATCH] ARM: OMAP: Allow I2C bus driver to be compiled as a module
Date: Wed, 18 Feb 2009 15:40:29 -0800 [thread overview]
Message-ID: <20090218234029.GB31436@atomide.com> (raw)
In-Reply-To: <20090218114525.cb95391f.jhnikula@gmail.com>
* Jarkko Nikula <jhnikula@gmail.com> [090218 01:42]:
> On Wed, 18 Feb 2009 11:22:18 +0200
> Aaro Koskinen <Aaro.Koskinen@nokia.com> wrote:
>
> > Fixes a linker error when OMAP I2C bus driver is compiled as a module:
> >
> > ERROR: "i2c_register_board_info" [arch/arm/plat-omap/i2c.ko]
> > undefined!
> >
> > The I2C utility functions used for board initialization should be
> > always built-in.
> >
> > Signed-off-by: Aaro Koskinen <Aaro.Koskinen@nokia.com>
> > ---
> > arch/arm/plat-omap/Makefile | 3 ++-
> > arch/arm/plat-omap/include/mach/common.h | 2 +-
> > 2 files changed, 3 insertions(+), 2 deletions(-)
> >
> Acked-by: Jarkko Nikula <jarkko.nikula@nokia.com>
Applying to linux-omap and omap-fixes.
Tony
next prev parent reply other threads:[~2009-02-18 23:40 UTC|newest]
Thread overview: 19+ 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
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 [this message]
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
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=20090218234029.GB31436@atomide.com \
--to=tony@atomide.com \
--cc=Aaro.Koskinen@nokia.com \
--cc=ext-atal.shargorodsky@nokia.com \
--cc=jarkko.nikula@nokia.com \
--cc=jhnikula@gmail.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