public inbox for linux-kernel@vger.kernel.org
 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 2/6] iio: adc: fix spelling mistakes in comments
Date: Sat, 7 Mar 2026 17:29:06 +0000	[thread overview]
Message-ID: <20260307172906.43d6f976@jic23-huawei> (raw)
In-Reply-To: <20260307104705.49129-3-i.shihao.999@gmail.com>

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

> There were several spelling mistakes in comments such

Just noticed you have a short wrap to commit descriptions.

Usual (not particularly well documented) convention is up to 75 chars
for these to allow for default git settings indenting them a few spaces.

Otherwise this looks good to me.

thanks,

Jonathan


> as mulitiply, referrence, ocurring, consequtive, and
> celcius, as well as other occurrences. Fix these spelling
> mistakes to improve code readability and consistency.
> 
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
> ---
>  drivers/iio/adc/ad4030.c           | 2 +-
>  drivers/iio/adc/ad4170-4.c         | 6 +++---
>  drivers/iio/adc/ad7380.c           | 2 +-
>  drivers/iio/adc/ad7887.c           | 2 +-
>  drivers/iio/adc/ad7923.c           | 4 ++--
>  drivers/iio/adc/at91_adc.c         | 4 ++--
>  drivers/iio/adc/max1363.c          | 2 +-
>  drivers/iio/adc/mcp3564.c          | 2 +-
>  drivers/iio/adc/men_z188_adc.c     | 2 +-
>  drivers/iio/adc/npcm_adc.c         | 2 +-
>  drivers/iio/adc/palmas_gpadc.c     | 2 +-
>  drivers/iio/adc/rohm-bd79124.c     | 4 ++--
>  drivers/iio/adc/spear_adc.c        | 2 +-
>  drivers/iio/adc/stm32-adc-core.c   | 2 +-
>  drivers/iio/adc/stm32-adc.c        | 2 +-
>  drivers/iio/adc/sun20i-gpadc-iio.c | 2 +-
>  drivers/iio/adc/ti_am335x_adc.c    | 2 +-
>  drivers/iio/adc/twl4030-madc.c     | 2 +-
>  drivers/iio/adc/twl6030-gpadc.c    | 2 +-
>  19 files changed, 24 insertions(+), 24 deletions(-)
> 

  reply	other threads:[~2026-03-07 17:29 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 [this message]
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
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=20260307172906.43d6f976@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