From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: BouziguesAlexis@johndeere.com,
Lucas Stankus <lucas.p.stankus@gmail.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lothar Rubusch <l.rubusch@gmail.com>,
linux@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] iio: accel: adxl313: add missing buffer selections in Kconfig
Date: Sun, 18 Oct 2026 20:38:19 +0100 [thread overview]
Message-ID: <20261018203819.48ff35f5@jic23-hlaptop> (raw)
In-Reply-To: <aszu6m0hclBWzPEv@nsa>
On Mon, 12 Oct 2026 15:30:50 +0100
Nuno Sá <nuno.sa@analog.com> wrote:
> On Tue, Oct 06, 2026 at 07:08:58PM -0500, Alexis Bouzigues via B4 Relay wrote:
> > From: Alexis Bouzigues <BouziguesAlexis@JohnDeere.com>
> >
> > The FIFO support added to the ADXL313 core uses
> > devm_iio_kfifo_buffer_setup() and iio_push_to_buffers(), but its Kconfig
> > entry does not select the required buffer support. Enabling either
> > frontend without IIO_BUFFER or IIO_KFIFO_BUF causes undefined references
> > to devm_iio_kfifo_buffer_setup_ext() and iio_push_to_buffers().
> >
> > Select IIO_BUFFER and IIO_KFIFO_BUF from the shared ADXL313 core symbol
> > so both the I2C and SPI frontends have the required dependencies.
> >
> > Fixes: ff8093fa6ba4 ("iio: accel: adxl313: add buffered FIFO watermark with interrupt handling")
> > Cc: stable@vger.kernel.org
> > Assisted-by: LLM
> > Signed-off-by: Alexis Bouzigues <BouziguesAlexis@JohnDeere.com>
> > ---
> > Add the buffer selections required by the ADXL313 FIFO support.
> > The shared core symbol covers both I2C and SPI frontends.
> > ---
>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
>
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
prev parent reply other threads:[~2026-10-18 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 0:08 Alexis Bouzigues via B4 Relay
2026-10-08 7:41 ` Joshua Crofts
2026-10-12 14:30 ` Nuno Sá
2026-10-18 19:38 ` 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=20261018203819.48ff35f5@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=BouziguesAlexis@johndeere.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=l.rubusch@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=lucas.p.stankus@gmail.com \
--cc=nuno.sa@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
all inboxes | Powered by JetHome®