From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: fix iio_push_to_buffers_with_ts() typo
Date: Thu, 24 Jul 2025 11:57:55 +0100 [thread overview]
Message-ID: <20250724115755.5affb98e@jic23-huawei> (raw)
In-Reply-To: <20250722-iio-fix-iio_push_to_buffer_with_ts-typo-v1-1-6ac9efb856d3@baylibre.com>
On Tue, 22 Jul 2025 16:52:38 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Replace iio_push_to_buffer_with_ts() with iio_push_to_buffers_with_ts()
> in some documentation comments in iio.h. The latter is the correct name
> of the function, the former doesn't exist.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
oops.
Applied to the testing branch of iio.git.
Thanks,
J
> ---
> include/linux/iio/iio.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index d11668f14a3e17654fcf17a4e853d4b493205019..2f5560646ee49052deaaaae1dd2b92b21c4d4fd5 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -779,7 +779,7 @@ static inline void *iio_device_get_drvdata(const struct iio_dev *indio_dev)
> * them safe for use with non-coherent DMA.
> *
> * A number of drivers also use this on buffers that include a 64-bit timestamp
> - * that is used with iio_push_to_buffer_with_ts(). Therefore, in the case where
> + * that is used with iio_push_to_buffers_with_ts(). Therefore, in the case where
> * DMA alignment is not sufficient for proper timestamp alignment, we align to
> * 8 bytes instead.
> */
> @@ -794,7 +794,7 @@ static inline void *iio_device_get_drvdata(const struct iio_dev *indio_dev)
> * @name: identifier name of the buffer
> * @count: number of elements in the buffer
> *
> - * Declares a buffer that is safe to use with iio_push_to_buffer_with_ts(). In
> + * Declares a buffer that is safe to use with iio_push_to_buffers_with_ts(). In
> * addition to allocating enough space for @count elements of @type, it also
> * allocates space for a s64 timestamp at the end of the buffer and ensures
> * proper alignment of the timestamp.
>
> ---
> base-commit: cd2731444ee4e35db76f4fb587f12d327eec5446
> change-id: 20250722-iio-fix-iio_push_to_buffer_with_ts-typo-7bf33a1aa365
>
> Best regards,
prev parent reply other threads:[~2025-07-24 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 21:52 [PATCH] iio: fix iio_push_to_buffers_with_ts() typo David Lechner
2025-07-24 10:57 ` 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=20250724115755.5affb98e@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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