Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: andriy.shevchenko@intel.com, andy@kernel.org,
	dlechner@baylibre.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, marcelo.schmitt@analog.com,
	mazziesaccount@gmail.com, nuno.sa@analog.com
Subject: Re: [PATCH v2 6/6] iio: common: fix spelling mistakes in comments
Date: Sat, 7 Mar 2026 17:32:30 +0000	[thread overview]
Message-ID: <20260307173230.543a9475@jic23-huawei> (raw)
In-Reply-To: <20260307104705.49129-7-i.shihao.999@gmail.com>

On Sat,  7 Mar 2026 16:17:05 +0530
Shi Hao <i.shihao.999@gmail.com> wrote:

> fix incorrect spelling in comments
> 
> - exepects -> expects
> - fuction -> function
> - theoritical -> theoretical
> - appopriate -> appropriate
> 
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
This one (and patch 4 that I don't think I replied to) looks good to me
but we aren't in a rush given where we are in the cycle so I'll wait for v3.

Leave it a few days before sending another version though as you may get
reviews from others + they may disagree with me :)

Jonathan

> ---
>  drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c   | 2 +-
>  drivers/iio/common/hid-sensors/hid-sensor-attributes.c | 2 +-
>  drivers/iio/common/inv_sensors/inv_sensors_timestamp.c | 2 +-
>  drivers/iio/common/ms_sensors/ms_sensors_i2c.c         | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> index 82cef4a12442..af8563fde0a3 100644
> --- a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> +++ b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> @@ -106,7 +106,7 @@ static int cros_ec_sensors_read(struct iio_dev *indio_dev,
> 		switch (st->core.type) {
> 		case MOTIONSENSE_TYPE_ACCEL:
> 			/*
> -			 * EC returns data in g, iio exepects m/s^2.
> +			 * EC returns data in g, iio expects m/s^2.
> 			 * Do not use IIO_G_TO_M_S_2 to avoid precision loss.
> 			 */
> 			*val = div_s64(val64 * 980665, 10);
> diff --git a/drivers/iio/common/hid-sensors/hid-sensor-attributes.c b/drivers/iio/common/hid-sensors/hid-sensor-attributes.c
> index a61428bfdce3..c115a72832b2 100644
> --- a/drivers/iio/common/hid-sensors/hid-sensor-attributes.c
> +++ b/drivers/iio/common/hid-sensors/hid-sensor-attributes.c
> @@ -346,7 +346,7 @@ int hid_sensor_write_raw_hyst_rel_value(struct hid_sensor_common *st,
>  EXPORT_SYMBOL_NS(hid_sensor_write_raw_hyst_rel_value, "IIO_HID");
> 
>  /*
> - * This fuction applies the unit exponent to the scale.
> + * This function applies the unit exponent to the scale.
>   * For example:
>   * 9.806650000 ->exp:2-> val0[980]val1[665000000]
>   * 9.000806000 ->exp:2-> val0[900]val1[80600000]
> diff --git a/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c b/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> index 97526ba87b93..4e50c03410d9 100644
> --- a/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> +++ b/drivers/iio/common/inv_sensors/inv_sensors_timestamp.c
> @@ -154,7 +154,7 @@ void inv_sensors_timestamp_interrupt(struct inv_sensors_timestamp *ts,
> 		valid = inv_update_chip_period(ts, period);
> 	}
> 
> -	/* no previous data, compute theoritical value from interrupt */
> +	/* no previous data, compute theoretical value from interrupt */
> 	if (ts->timestamp == 0) {
> 		/* elapsed time: sensor period * sensor samples number */
> 		interval = (int64_t)ts->period * (int64_t)sample_nb;
> diff --git a/drivers/iio/common/ms_sensors/ms_sensors_i2c.c b/drivers/iio/common/ms_sensors/ms_sensors_i2c.c
> index 588470863681..1960a2ce82a8 100644
> --- a/drivers/iio/common/ms_sensors/ms_sensors_i2c.c
> +++ b/drivers/iio/common/ms_sensors/ms_sensors_i2c.c
> @@ -96,7 +96,7 @@ EXPORT_SYMBOL_NS(ms_sensors_read_prom_word, "IIO_MEAS_SPEC_SENSORS");
>   *
>   * Generic ADC conversion & read function for Measurement Specialties
>   * devices.
> - * The function will issue conversion command, sleep appopriate delay, and
> + * The function will issue conversion command, sleep appropriate delay, and
>   * issue command to read ADC.
>   *
>   * Return: 0 on success, negative errno otherwise.
> --
> 2.53.0


  reply	other threads:[~2026-03-07 17:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 10:46 [PATCH v2 0/6] iio: fix spelling mistakes in comments Shi Hao
2026-03-07 10:47 ` [PATCH v2 1/6] iio: accel: " Shi Hao
2026-03-07 17:24   ` Jonathan Cameron
2026-03-07 10:47 ` [PATCH v2 2/6] iio: adc: " Shi Hao
2026-03-07 17:29   ` Jonathan Cameron
2026-03-07 10:47 ` [PATCH v2 3/6] iio: amplifiers: fix spelling mistake in comment Shi Hao
2026-03-07 17:29   ` Jonathan Cameron
2026-03-07 10:47 ` [PATCH v2 4/6] iio: cdc: fix spelling mistakes in comments Shi Hao
2026-03-08 20:22   ` Andy Shevchenko
2026-03-07 10:47 ` [PATCH v2 5/6] iio: chemical: fix spelling mistake in comment Shi Hao
2026-03-07 17:30   ` Jonathan Cameron
2026-03-07 10:47 ` [PATCH v2 6/6] iio: common: fix spelling mistakes in comments Shi Hao
2026-03-07 17:32   ` Jonathan Cameron [this message]
2026-03-10  9:14 ` [PATCH v2 0/6] iio: " Matti Vaittinen

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=20260307173230.543a9475@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=i.shihao.999@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt@analog.com \
    --cc=mazziesaccount@gmail.com \
    --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