From: Lars-Peter Clausen <lars@metafoo.de>
To: Arnd Bergmann <arnd@arndb.de>, Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, Peter Meerwald <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>
Subject: Re: [next:master 1712/3346] ERROR: "iio_trigger_notify_done" [drivers/staging/iio/iio_dummy.ko] undefined!
Date: Mon, 09 Mar 2015 09:57:40 +0100 [thread overview]
Message-ID: <54FD6084.7000704@metafoo.de> (raw)
In-Reply-To: <2530839.vrY3not473@wuerfel>
On 03/09/2015 09:55 AM, Arnd Bergmann wrote:
> On Monday 09 March 2015 09:27:06 Fengguang Wu wrote:
>> On Sun, Mar 08, 2015 at 11:11:31PM +0100, Arnd Bergmann wrote:
>>> On Sunday 08 March 2015 05:31:03 kbuild test robot wrote:
>>>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>>> head: 28855005be1d6a0a041de46fd2e61da2b796abff
>>>> commit: 3608688973e8c85fbcd9b7e72b90e224b8d01526 [1712/3346] iio: ak8975: fix AK09911 dependencies
>>>> config: x86_64-randconfig-iv1-03080434 (attached as .config)
>>>> reproduce:
>>>> git checkout 3608688973e8c85fbcd9b7e72b90e224b8d01526
>>>> # save the attached .config to linux build tree
>>>> make ARCH=x86_64
>>>>
>>>> All error/warnings:
>>>>
>>>>>> ERROR: "iio_trigger_notify_done" [drivers/staging/iio/iio_dummy.ko] undefined!
>>>>>> ERROR: "iio_triggered_buffer_postenable" [drivers/staging/iio/iio_dummy.ko] undefined!
>>>>>> ERROR: "iio_triggered_buffer_predisable" [drivers/staging/iio/iio_dummy.ko] undefined!
>>>>>> ERROR: "iio_alloc_pollfunc" [drivers/staging/iio/iio_dummy.ko] undefined!
>>>>>> ERROR: "iio_dealloc_pollfunc" [drivers/staging/iio/iio_dummy.ko] undefined!
>>>>
>>>
>>> I don't understand what that error has to do with my patch, it
>>> seems like a separate issue.
>>
>> Arnd, they should be old link errors exposed by your build fix (which
>> enables the build to progress further).
>>
>
> Ok, makes sense. For some reason, I never see this particular error on ARM,
> otherwise I'd already have a fix for it.
Fengguang do you still have the config that triggered this build error?
Thanks,
- Lars
next prev parent reply other threads:[~2015-03-09 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201503080501.uKS2e4HY%fengguang.wu@intel.com>
2015-03-08 22:11 ` [next:master 1712/3346] ERROR: "iio_trigger_notify_done" [drivers/staging/iio/iio_dummy.ko] undefined! Arnd Bergmann
2015-03-09 1:27 ` Fengguang Wu
2015-03-09 8:55 ` Arnd Bergmann
2015-03-09 8:57 ` Lars-Peter Clausen [this message]
2015-03-09 9:09 ` Fengguang Wu
2015-03-09 10:02 ` Daniel Baluta
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=54FD6084.7000704@metafoo.de \
--to=lars@metafoo.de \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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