From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: nuno.sa@analog.com, linux-iio@vger.kernel.org,
Olivier Moysan <olivier.moysan@foss.st.com>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 0/2] iio: small fixes and improvements
Date: Sat, 22 Feb 2025 14:23:26 +0000 [thread overview]
Message-ID: <20250222142326.785847e7@jic23-huawei> (raw)
In-Reply-To: <4bf45120-d9f5-4c31-811b-655962984ba1@baylibre.com>
On Tue, 18 Feb 2025 11:29:08 -0600
David Lechner <dlechner@baylibre.com> wrote:
> On 2/18/25 4:31 AM, Nuno Sá via B4 Relay wrote:
> > The first patch is a fix for the backend code dealing with
> > direct_register_access. We need to properly terminate the received
> > string before passing it to sscanf().
> >
> > The second patch is about using the simple_write_to_buffer() which makes
> > the direct_register_access write side more symmetric with the read side.
> >
> > ---
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
>
Applied
prev parent reply other threads:[~2025-02-22 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 10:31 [PATCH 0/2] iio: small fixes and improvements Nuno Sá
2025-02-18 10:31 ` Nuno Sá via B4 Relay
2025-02-18 10:31 ` [PATCH 1/2] iio: backend: make sure to NULL terminate stack buffer Nuno Sá
2025-02-18 10:31 ` Nuno Sá via B4 Relay
2025-02-18 15:52 ` David Lechner
2025-02-18 16:36 ` Nuno Sá
2025-02-18 16:57 ` David Lechner
2025-02-18 10:31 ` [PATCH 2/2] iio: core: make use of simple_write_to_buffer() Nuno Sá
2025-02-18 10:31 ` Nuno Sá via B4 Relay
2025-02-18 17:29 ` [PATCH 0/2] iio: small fixes and improvements David Lechner
2025-02-22 14:23 ` 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=20250222142326.785847e7@jic23-huawei \
--to=jic23@kernel.org \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.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 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.