From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] iio: Implement counter channel type and info constants
Date: Thu, 15 Sep 2016 10:03:43 -0400 [thread overview]
Message-ID: <20160915140343.GA19015@sophia> (raw)
In-Reply-To: <201609152127.xNcZs3aX%fengguang.wu@intel.com>
On Thu, Sep 15, 2016 at 09:35:57PM +0800, kbuild test robot wrote:
>Hi William,
>
>[auto build test ERROR on iio/togreg]
>[also build test ERROR on v4.8-rc6 next-20160915]
>[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
>[Check https://git-scm.com/docs/git-format-patch for more information]
>
>url: https://github.com/0day-ci/linux/commits/William-Breathitt-Gray/Add-IIO-support-for-counter-devices/20160915-032651
>base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
>config: x86_64-randconfig-s1-09151924 (attached as .config)
>compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
>reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
>Note: the linux-review/William-Breathitt-Gray/Add-IIO-support-for-counter-devices/20160915-032651 HEAD 9dfaeb5dd7e5fffaedaaaa34c80c7790ed346b72 builds fine.
> It only hurts bisectibility.
>
>All errors (new ones prefixed by >>):
>
>>> ld: cannot find drivers/iio/counter/built-in.o: No such file or directory
>
>---
>0-DAY kernel test infrastructure Open Source Technology Center
>https://lists.01.org/pipermail/kbuild-all Intel Corporation
I moved the creation of the "counter" subdirectory to this first patch,
but the 104-QUAD-8 driver is only added in the subsequent patch;
effectively, the non-populated Makefile in this patch leads to the
error.
I'll submit version 3 of this patchset with the "counter" subdirectory
introduced in the same patch as the 104-QUAD-8 driver. That should
resolve this issue.
William Breathitt Gray
next prev parent reply other threads:[~2016-09-15 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 19:24 [PATCH v2 0/2] Add IIO support for counter devices William Breathitt Gray
2016-09-14 19:24 ` [PATCH v2 1/2] iio: Implement counter channel type and info constants William Breathitt Gray
2016-09-15 13:35 ` kbuild test robot
2016-09-15 14:03 ` William Breathitt Gray [this message]
2016-09-15 22:30 ` kbuild test robot
2016-09-14 19:24 ` [PATCH v2 2/2] iio: 104-quad-8: Add IIO support for the ACCES 104-QUAD-8 William Breathitt Gray
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=20160915140343.GA19015@sophia \
--to=vilhelm.gray@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).