From: Joshua Crofts <joshua.crofts1@gmail.com>
To: David Lechner <dlechner@baylibre.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Stefan Popa" <stefan.popa@analog.com>,
"Julien Stephan" <jstephan@baylibre.com>,
"Ivan Mikhaylov" <fr0st61te@gmail.com>,
"Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Marilene Andrade Garcia" <marilene.agarcia@gmail.com>,
"Kim Seer Paller" <kimseer.paller@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: adc: ad7380: add missing 'select REGMAP' to Kconfig
Date: Wed, 8 Jul 2026 16:45:55 +0200 [thread overview]
Message-ID: <20260708164555.0000602e@gmail.com> (raw)
In-Reply-To: <6d8c6b4b-89b3-431b-a31a-11de654c2901@baylibre.com>
On Wed, 8 Jul 2026 09:32:24 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 7/8/26 12:34 AM, Joshua Crofts wrote:
> > The Kconfig entry for the AD7380 is missing a 'select REGMAP'
> > parameter, causing build failures.
>
> This one has already been fixed.
>
> https://lore.kernel.org/linux-iio/20260603134955.2f1d5ede@jic23-huawei/
>
> Suggest to use linux-next for development so you get both the fixes-togreg
> branch and the regular togreg branch.
Ugh, my bad, I only use the testing branch in the IIO tree.
Thanks
--
Kind regards
CJD
next prev parent reply other threads:[~2026-07-08 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 5:34 [PATCH 0/3] iio: adc: add missing 'select REGMAP' to Kconfig Joshua Crofts
2026-07-08 5:34 ` [PATCH 1/3] iio: adc: ad7380: " Joshua Crofts
2026-07-08 14:32 ` David Lechner
2026-07-08 14:45 ` Joshua Crofts [this message]
2026-07-08 5:34 ` [PATCH 2/3] iio: adc: max34408: add missing 'select REGMAP_I2C' " Joshua Crofts
2026-07-08 5:34 ` [PATCH 3/3] iio: adc: max14001: add missing 'select REGMAP' " Joshua Crofts
2026-07-08 7:47 ` [PATCH 0/3] iio: adc: " Andy Shevchenko
2026-07-08 8:01 ` Joshua Crofts
2026-07-08 10:54 ` Andy Shevchenko
2026-07-08 10:55 ` Andy Shevchenko
2026-07-10 0:04 ` Jonathan Cameron
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=20260708164555.0000602e@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=fr0st61te@gmail.com \
--cc=jic23@kernel.org \
--cc=jstephan@baylibre.com \
--cc=kimseer.paller@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marilene.agarcia@gmail.com \
--cc=nuno.sa@analog.com \
--cc=stable@vger.kernel.org \
--cc=stefan.popa@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