Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Anas Khan <anxkhn28@gmail.com>
Cc: Nuno Sa <nuno.sa@analog.com>, Jonathan Cameron <jic23@kernel.org>,
	 Olivier Moysan <olivier.moysan@foss.st.com>,
	David Lechner <dlechner@baylibre.com>,
	 Andy Shevchenko <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: backend: fix typos in comments
Date: Thu, 2 Jul 2026 13:23:54 +0100	[thread overview]
Message-ID: <akZYSPu2YruEFr3R@nsa> (raw)
In-Reply-To: <20260702101129.62445-1-anxkhn28@gmail.com>

On Thu, Jul 02, 2026 at 03:41:29PM +0530, Anas Khan wrote:
> Fix several comment typos in industrialio-backend.c: correct "through"
> in a channel-spec comment, "initiates a process" in the activation
> comment, and drop a stray apostrophe from "Gets" in two getter
> kerneldoc comments.
> 
> Signed-off-by: Anas Khan <anxkhn28@gmail.com>
> ---

Reviewed-by: Nuno Sá <nuno.sa@analog.com>

>  drivers/iio/industrialio-backend.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-backend.c
> index 4763e224ebc6..f7a4be8ec320 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -649,7 +649,7 @@ EXPORT_SYMBOL_NS_GPL(iio_backend_ext_info_get, "IIO_BACKEND");
>   * @len: Buffer length
>   *
>   * This helper is intended to be used by backends that extend an IIO channel
> - * (trough iio_backend_extend_chan_spec()) with extended info. In that case,
> + * (through iio_backend_extend_chan_spec()) with extended info. In that case,
>   * backends are not supposed to give their own callbacks (as they would not have
>   * a way to get the backend from indio_dev). This is the setter.
>   *
> @@ -851,7 +851,7 @@ EXPORT_SYMBOL_NS_GPL(iio_backend_filter_type_set, "IIO_BACKEND");
>   * @back: Backend device
>   * @timeout_us: Timeout value in us.
>   *
> - * When activated, it initates a proccess that aligns the sample's most
> + * When activated, it initiates a process that aligns the sample's most
>   * significant bit (MSB) based solely on the captured data, without
>   * considering any other external signals.
>   *
> @@ -1017,7 +1017,7 @@ static struct iio_backend *__devm_iio_backend_fwnode_get(struct device *dev, con
>   * @dev: Consumer device for the backend
>   * @name: Backend name
>   *
> - * Get's the backend associated with @dev.
> + * Gets the backend associated with @dev.
>   *
>   * RETURNS:
>   * A backend pointer, negative error pointer otherwise.
> @@ -1050,7 +1050,7 @@ EXPORT_SYMBOL_NS_GPL(devm_iio_backend_get_by_index, "IIO_BACKEND");
>   * @name: Backend name
>   * @fwnode: Firmware node of the backend consumer
>   *
> - * Get's the backend associated with a firmware node.
> + * Gets the backend associated with a firmware node.
>   *
>   * RETURNS:
>   * A backend pointer, negative error pointer otherwise.
> -- 
> 2.54.0
> 

      parent reply	other threads:[~2026-07-02 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 10:11 [PATCH] iio: backend: fix typos in comments Anas Khan
2026-07-02 11:06 ` Andy Shevchenko
2026-07-02 16:56   ` Jonathan Cameron
2026-07-02 12:23 ` Nuno Sá [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=akZYSPu2YruEFr3R@nsa \
    --to=noname.nuno@gmail.com \
    --cc=andy@kernel.org \
    --cc=anxkhn28@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox