On Mon, Mar 9, 2015 at 11:09 AM, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote: > On Mon, Mar 09, 2015 at 09:57:40AM +0100, Lars-Peter Clausen wrote: >> 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? > > Yes, attached. OK, drivers/staging/iio/Kconfig is missing a 'select TRIGGER' for config IIO_SIMPLE_DUMMY_BUFFER. I will send a patch asap :). thanks, Daniel. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
