From: Jonathan Cameron <jic23@kernel.org>
To: kbuild test robot <lkp@intel.com>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: kbuild-all@01.org, linux@armlinux.org.uk, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
mark.rutland@arm.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@st.com, lars@metafoo.de, knaack.h@gmx.de,
pmeerw@pmeerw.net, benjamin.gaignard@linaro.org,
benjamin.gaignard@st.com
Subject: Re: [PATCH 2/7] iio: adc: stm32: Enable use of stm32 timer triggers
Date: Sat, 21 Jan 2017 12:55:56 +0000 [thread overview]
Message-ID: <c2042413-c47d-c31c-2890-3b626829f478@kernel.org> (raw)
In-Reply-To: <201701200712.zoWuIMA4%fengguang.wu@intel.com>
On 19/01/17 23:31, kbuild test robot wrote:
> Hi Fabrice,
>
> [auto build test ERROR on next-20170119]
> [also build test ERROR on v4.10-rc4]
> [cannot apply to iio/togreg robh/for-next v4.9-rc8 v4.9-rc7 v4.9-rc6]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Fabrice-Gasnier/Add-support-for-triggered-buffer-mode-to-STM32-ADC/20170120-062214
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
There is a precursor patch set mentioned in the cover letter. Not sure there is
a sensible automated way to deal with that!
Jonathan
>
> All errors (new ones prefixed by >>):
>
>>> drivers/iio/adc/stm32-adc.c:26:49: fatal error: linux/iio/timer/stm32-timer-trigger.h: No such file or directory
> #include <linux/iio/timer/stm32-timer-trigger.h>
> ^
> compilation terminated.
>
> vim +26 drivers/iio/adc/stm32-adc.c
>
> 20 */
> 21
> 22 #include <linux/clk.h>
> 23 #include <linux/delay.h>
> 24 #include <linux/iio/iio.h>
> 25 #include <linux/iio/buffer.h>
> > 26 #include <linux/iio/timer/stm32-timer-trigger.h>
> 27 #include <linux/iio/trigger.h>
> 28 #include <linux/iio/trigger_consumer.h>
> 29 #include <linux/iio/triggered_buffer.h>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2017-01-21 12:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 13:34 [PATCH 0/7] Add support for triggered buffer mode to STM32 ADC Fabrice Gasnier
2017-01-19 13:34 ` [PATCH 1/7] iio: adc: stm32: add support for triggered buffer mode Fabrice Gasnier
2017-01-22 12:53 ` Jonathan Cameron
[not found] ` <2c683b78-6c78-3224-0646-37793deba0e9@st.com>
2017-01-28 14:02 ` Jonathan Cameron
2017-01-19 13:34 ` [PATCH 2/7] iio: adc: stm32: Enable use of stm32 timer triggers Fabrice Gasnier
2017-01-19 23:31 ` kbuild test robot
2017-01-21 12:55 ` Jonathan Cameron [this message]
2017-01-22 12:55 ` Jonathan Cameron
2017-01-24 14:37 ` Fabrice Gasnier
2017-01-28 12:46 ` Jonathan Cameron
2017-01-19 13:34 ` [PATCH 3/7] iio: adc: stm32: add trigger polarity extended attribute Fabrice Gasnier
2017-01-22 12:58 ` Jonathan Cameron
2017-01-24 14:41 ` Fabrice Gasnier
2017-01-19 13:34 ` [PATCH 4/7] Documentation: dt: iio: stm32-adc: optional dma support Fabrice Gasnier
2017-01-21 20:54 ` Rob Herring
2017-01-19 13:34 ` [PATCH 5/7] iio: adc: stm32: add " Fabrice Gasnier
2017-01-22 13:14 ` Jonathan Cameron
2017-01-24 14:43 ` Fabrice Gasnier
2017-01-24 18:25 ` Jonathan Cameron
2017-01-19 13:34 ` [PATCH 6/7] ARM: dts: stm32: Enable dma by default on stm32f4 adc Fabrice Gasnier
2017-01-19 13:34 ` [PATCH 7/7] ARM: dts: stm32: Enable pwm1 and pwm3 for stm32f469-eval Fabrice Gasnier
2017-01-20 0:09 ` kbuild test robot
2017-01-20 10:19 ` Alexandre Torgue
2017-01-20 10:36 ` Fabrice Gasnier
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=c2042413-c47d-c31c-2890-3b626829f478@kernel.org \
--to=jic23@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).