From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: jic23@kernel.org, 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 v3 2/6] iio: adc: fix spelling mistakes in comments
Date: Mon, 9 Mar 2026 13:52:25 +0200 [thread overview]
Message-ID: <aa60eapboLEbFaFN@ashevche-desk.local> (raw)
In-Reply-To: <20260309104513.40359-3-i.shihao.999@gmail.com>
On Mon, Mar 09, 2026 at 04:15:09PM +0530, Shi Hao wrote:
> There were several spelling mistakes in comments such as mulitiply,
> referrence, ocurring, consequtive, and celcius, as well as other
> occurrences. Fix these spelling mistakes to improve code readability
> and consistency.
...
> static u8 twl6032_channel_to_reg(int channel)
> {
> /*
> * for any prior chosen channel, when the conversion is ready
While at it,
for --> For
> - * the result is avalable in GPCH0_LSB, GPCH0_MSB.
> + * the result is available in GPCH0_LSB, GPCH0_MSB.
> */
>
> return TWL6032_GPADC_GPCH0_LSB;
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-09 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 10:45 [PATCH v3 0/6] iio: fix spelling mistakes in comments Shi Hao
2026-03-09 10:45 ` [PATCH v3 1/6] iio: accel: fix typo celcius to Celsius Shi Hao
2026-03-09 10:45 ` [PATCH v3 2/6] iio: adc: fix spelling mistakes in comments Shi Hao
2026-03-09 11:52 ` Andy Shevchenko [this message]
2026-03-09 10:45 ` [PATCH v3 3/6] iio: amplifiers: fix typo Curren to Current Shi Hao
2026-03-09 11:44 ` Andy Shevchenko
2026-03-09 10:45 ` [PATCH v3 4/6] iio: cdc: fix spelling mistakes in comments Shi Hao
2026-03-09 11:43 ` Andy Shevchenko
2026-03-09 19:32 ` Jonathan Cameron
2026-03-09 10:45 ` [PATCH v3 5/6] iio: chemical: fix typo insuffient to insufficient Shi Hao
2026-03-09 11:42 ` Andy Shevchenko
2026-03-09 10:45 ` [PATCH v3 6/6] iio: common: fix spelling mistakes in comments Shi Hao
2026-03-09 11:40 ` Andy Shevchenko
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=aa60eapboLEbFaFN@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=i.shihao.999@gmail.com \
--cc=jic23@kernel.org \
--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