From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Cristian Pop" <cristian.pop@analog.com>,
"Mircea Caprioru" <mircea.caprioru@analog.com>,
"Alexandru Tachici" <alexandru.tachici@analog.com>,
"Marcus Folkesson" <marcus.folkesson@gmail.com>,
"Fabrice Gasnier" <fabrice.gasnier@st.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] iio: resolver: ad2s1210 add missing select REGMAP in Kconfig
Date: Sun, 6 Oct 2024 14:24:37 +0100 [thread overview]
Message-ID: <20241006142437.7209f801@jic23-huawei> (raw)
In-Reply-To: <a322e7c6-2944-4159-9632-bbccdc0b56fe@baylibre.com>
On Thu, 3 Oct 2024 17:44:03 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 10/3/24 11:49 AM, Javier Carrasco wrote:
> > This driver makes use of regmap, but does not select the required
> > module.
> > Add the missing 'select REGMAP'.
> >
> > Fixes: b3689e14415a ("staging: iio: resolver: ad2s1210: use regmap for config registers")
> > Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> > ---
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
Applied to the fixes-togreg branch of iio.git.
Thanks,
J
next prev parent reply other threads:[~2024-10-06 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 16:49 [PATCH 0/8] iio: {amplifiers,dac,frequency,resolver}: add missing selects in Kconfig Javier Carrasco
2024-10-03 16:49 ` [PATCH 1/8] iio: resolver: ad2s1210 add missing select REGMAP " Javier Carrasco
2024-10-03 22:44 ` David Lechner
2024-10-06 13:24 ` Jonathan Cameron [this message]
2024-10-03 16:49 ` [PATCH 2/8] iio: resolver: ad2s1210: add missing select (TRIGGERED_)BUFFER " Javier Carrasco
2024-10-03 22:44 ` David Lechner
2024-10-06 13:25 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 3/8] iio: frequency: adf4377: add missing select REMAP_SPI " Javier Carrasco
2024-10-06 13:26 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 4/8] iio: frequency: admv4420: " Javier Carrasco
2024-10-03 19:30 ` Javier Carrasco
2024-10-06 13:23 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 5/8] iio: amplifiers: ada4250: add missing select REGMAP_SPI " Javier Carrasco
2024-10-06 13:29 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 6/8] iio: dac: ad5770r: " Javier Carrasco
2024-10-06 13:28 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 7/8] iio: dac: ltc1660: " Javier Carrasco
2024-10-06 13:30 ` Jonathan Cameron
2024-10-03 16:49 ` [PATCH 8/8] iio: dac: stm32-dac-core: add missing select REGMAP_MMIO " Javier Carrasco
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=20241006142437.7209f801@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandru.tachici@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=cristian.pop@analog.com \
--cc=dlechner@baylibre.com \
--cc=fabrice.gasnier@st.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=mircea.caprioru@analog.com \
--cc=nuno.sa@analog.com \
/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).