From: Wolfram Sang <wsa@the-dreams.de>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: "Grygorii Strashko" <grygorii.strashko@ti.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Alexander Sverdlin" <alexander.sverdlin@nokia.com>,
linux-i2c@vger.kernel.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: i2c-davinci build failure with Linux v4.0-3843-gbb0fd7ab0986
Date: Wed, 15 Apr 2015 21:07:57 +0200 [thread overview]
Message-ID: <20150415190757.GD1125@katana> (raw)
In-Reply-To: <CA+5PVA7Fzw4m1qqj2nHCzP4JJFZnis-6=kQehAbt0a-RJiF73A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Wed, Apr 15, 2015 at 12:33:57PM -0400, Josh Boyer wrote:
> Hi All,
>
> The i2c-davinci driver failed to build as a module with Linus' latest
> tree as of this morning. The error was:
>
> ERROR: "i2c_generic_gpio_recovery" [drivers/i2c/busses/i2c-davinci.ko]
> undefined!
> ERROR: "i2c_generic_scl_recovery" [drivers/i2c/busses/i2c-davinci.ko] undefined!
> ERROR: "i2c_recover_bus" [drivers/i2c/busses/i2c-davinci.ko] undefined!
> scripts/Makefile.modpost:90: recipe for target '__modpost' failed
>
> It looks like commit 2e65676f710e (i2c: davinci: use bus recovery
> infrastructure) likely introduced this error. None of the i2c bus
> recovery functions are exported from i2c-core.c that I can tell.
>
> Was this commit tested as a modular build?
How embarassing. I meanwhile rely on the build-bots to do module
testing, but this failed here :( A patch was sent to -next a second ago
and I will send a pull-request to Linus ASAP. Thanks for the report!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-04-15 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 16:33 i2c-davinci build failure with Linux v4.0-3843-gbb0fd7ab0986 Josh Boyer
2015-04-15 19:07 ` Wolfram Sang [this message]
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=20150415190757.GD1125@katana \
--to=wsa@the-dreams.de \
--cc=alexander.sverdlin@nokia.com \
--cc=grygorii.strashko@ti.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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