From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Santos" <Jonathan.Santos@analog.com>,
"Ramona Alexandra Nechita" <ramona.nechita@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: adc: add missing 'select IIO_TRIGGERED_BUFFER' to Kconfig entries
Date: Thu, 2 Jul 2026 14:02:36 +0300 [thread overview]
Message-ID: <akZFTC6qVzLG5ton@ashevche-desk.local> (raw)
In-Reply-To: <20260701-add-adc-kconfig-deps-v1-0-b9708d74f426@gmail.com>
On Wed, Jul 01, 2026 at 09:21:45PM +0200, Joshua Crofts wrote:
> The AD4130 and AD7779 entries are missing 'select IIO_TRIGGERED_BUFFER'
> entries, causing potential build failures.
>
> Steps to reproduce:
> 1. Run `make allnoconfig`
> 2. Run `make menuconfig` and select any afformentioned driver and
> modules it depends on.
> 3. Run `make .` and the build will fail due to missing triggered
> buffer definitions etc.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> I seem to have stumbled upon a lot of drivers which have incomplete
> Kconfigs, expect more patch series per sensor type.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-02 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 19:21 [PATCH 0/2] iio: adc: add missing 'select IIO_TRIGGERED_BUFFER' to Kconfig entries Joshua Crofts
2026-07-01 19:21 ` [PATCH 1/2] iio: adc: ad4130: add missing `select IIO_TRIGGERED_BUFFER` to Kconfig Joshua Crofts
2026-07-01 19:21 ` [PATCH 2/2] iio: adc: ad7779: add missing 'select IIO_TRIGGERED_BUFFER' " Joshua Crofts
2026-07-02 11:03 ` Andy Shevchenko
2026-07-02 11:02 ` Andy Shevchenko [this message]
2026-07-02 17:05 ` [PATCH 0/2] iio: adc: add missing 'select IIO_TRIGGERED_BUFFER' to Kconfig entries 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=akZFTC6qVzLG5ton@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Jonathan.Santos@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.nechita@analog.com \
--cc=stable@vger.kernel.org \
/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