From: Jonathan Cameron <jic23@kernel.org>
To: "Petr Štetiar" <ynezz@true.cz>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Tomasz Duszynski <tduszyns@gmail.com>,
stable@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: chemical: sps30: fix missing triggered buffer dependency
Date: Sun, 1 Mar 2020 14:24:07 +0000 [thread overview]
Message-ID: <20200301142407.0e63f6dc@archlinux> (raw)
In-Reply-To: <20200227162734.604-1-ynezz@true.cz>
On Thu, 27 Feb 2020 17:27:34 +0100
Petr Štetiar <ynezz@true.cz> wrote:
> SPS30 uses triggered buffer, but the dependency is not specified in the
> Kconfig file. Fix this by selecting IIO_BUFFER and IIO_TRIGGERED_BUFFER
> config symbols.
>
> Cc: stable@vger.kernel.org
> Fixes: 232e0f6ddeae ("iio: chemical: add support for Sensirion SPS30 sensor")
> Signed-off-by: Petr Štetiar <ynezz@true.cz>
Applied to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/iio/chemical/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iio/chemical/Kconfig b/drivers/iio/chemical/Kconfig
> index 0b91de4df8f4..a7e65a59bf42 100644
> --- a/drivers/iio/chemical/Kconfig
> +++ b/drivers/iio/chemical/Kconfig
> @@ -91,6 +91,8 @@ config SPS30
> tristate "SPS30 particulate matter sensor"
> depends on I2C
> select CRC8
> + select IIO_BUFFER
> + select IIO_TRIGGERED_BUFFER
> help
> Say Y here to build support for the Sensirion SPS30 particulate
> matter sensor.
prev parent reply other threads:[~2020-03-01 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 16:27 [PATCH] iio: chemical: sps30: fix missing triggered buffer dependency Petr Štetiar
2020-03-01 14:24 ` 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=20200301142407.0e63f6dc@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--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 \
--cc=stable@vger.kernel.org \
--cc=tduszyns@gmail.com \
--cc=ynezz@true.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.