From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Tilman Schmidt <tilman-ZTO5kqT2PaM@public.gmane.org>
Cc: LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 2.6.31-rc1 build failure: i2c-designware.ko
Date: Sun, 28 Jun 2009 21:01:18 +0200 [thread overview]
Message-ID: <20090628210118.15739fbc@hyperion.delvare> (raw)
In-Reply-To: <4A47BB88.3090407-ZTO5kqT2PaM@public.gmane.org>
On Sun, 28 Jun 2009 20:50:48 +0200, Tilman Schmidt wrote:
> I encountered this modpost failure building 2.6.31-rc1:
>
> Kernel: arch/x86/boot/bzImage is ready (#2)
> Building modules, stage 2.
> MODPOST 1218 modules
> ERROR: "clk_enable" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_get" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_put" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_disable" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_get_rate" [drivers/i2c/busses/i2c-designware.ko] undefined!
> WARNING: modpost: Found 12 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[1]: *** [__modpost] Fehler 1
> make: *** [modules] Fehler 2
>
> Config attatched.
Already reported half a dozen times, and already fixed:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=47749b14e55cd167632f9a27a4fc439e591e5268
--
Jean Delvare
next prev parent reply other threads:[~2009-06-28 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 18:50 2.6.31-rc1 build failure: i2c-designware.ko Tilman Schmidt
[not found] ` <4A47BB88.3090407-ZTO5kqT2PaM@public.gmane.org>
2009-06-28 19:01 ` Jean Delvare [this message]
[not found] ` <20090628210118.15739fbc-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-06-28 21:36 ` Tilman Schmidt
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=20090628210118.15739fbc@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tilman-ZTO5kqT2PaM@public.gmane.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;
as well as URLs for NNTP newsgroup(s).