From: Jonathan Cameron <jic23@kernel.org>
To: Alexander Wuerstlein <arw@arw.name>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] iio hid-sensor-trigger: add Kconfig depends on IIO_BUFFER
Date: Tue, 13 Jun 2017 21:13:22 +0100 [thread overview]
Message-ID: <20170613211322.5ed84610@kernel.org> (raw)
In-Reply-To: <20170612115608.28058-1-arw@arw.name>
On Mon, 12 Jun 2017 13:56:05 +0200
Alexander Wuerstlein <arw@arw.name> wrote:
> Building a kernel with my configuration failed with:
> > drivers/built-in.o: In function `hid_sensor_setup_batch_mode': staging/drivers/iio/common/hid-sensors/hid-sensor-trigger.c:104: undefined reference to `iio_buffer_set_attrs'
> which is fixed by this patch.
>
> Signed-off-by: Alexander Wuerstlein <arw@arw.name>
Added a fixes tag as the issue was only introduced very recently.
Applied to the togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/iio/common/hid-sensors/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/common/hid-sensors/Kconfig b/drivers/iio/common/hid-sensors/Kconfig
> index 39188b72cd3b..80105378b0ba 100644
> --- a/drivers/iio/common/hid-sensors/Kconfig
> +++ b/drivers/iio/common/hid-sensors/Kconfig
> @@ -16,7 +16,7 @@ config HID_SENSOR_IIO_COMMON
>
> config HID_SENSOR_IIO_TRIGGER
> tristate "Common module (trigger) for all HID Sensor IIO drivers"
> - depends on HID_SENSOR_HUB && HID_SENSOR_IIO_COMMON
> + depends on HID_SENSOR_HUB && HID_SENSOR_IIO_COMMON && IIO_BUFFER
> select IIO_TRIGGER
> help
> Say yes here to build trigger support for HID sensors.
prev parent reply other threads:[~2017-06-13 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 11:56 [PATCH] iio hid-sensor-trigger: add Kconfig depends on IIO_BUFFER Alexander Wuerstlein
2017-06-13 20:13 ` Jonathan Cameron [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=20170613211322.5ed84610@kernel.org \
--to=jic23@kernel.org \
--cc=arw@arw.name \
--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).