From: Shi Hao <i.shihao.999@gmail.com>
To: andriy.shevchenko@intel.com
Cc: andy@kernel.org, dlechner@baylibre.com, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
marcelo.schmitt@analog.com, mazziesaccount@gmail.com,
nuno.sa@analog.com, i.shihao.999@gmail.com
Subject: [PATCH v2 0/6] iio: fix spelling mistakes in comments
Date: Sat, 7 Mar 2026 16:16:59 +0530 [thread overview]
Message-ID: <20260307104705.49129-1-i.shihao.999@gmail.com> (raw)
This series fixes spelling mistakes in comments across
several IIO subsystems to improve readability and code
consistency.
v2:
- Split original patch into 6 commits
- Fixed commit message formatting and typos
- Added necessary tags in commits
- Added more fixes then previous
Shi Hao (6):
iio: accel: fix spelling mistakes in comments
iio: adc: fix spelling mistakes in comments
iio: amplifiers: fix spelling mistake in comment
iio: cdc: fix spelling mistakes in comments
iio: chemical: fix spelling mistake in comment
iio: common: fix spelling mistakes in comments
drivers/iio/accel/adis16201.c | 2 +-
drivers/iio/accel/adis16209.c | 2 +-
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 +-
drivers/iio/amplifiers/ada4250.c | 2 +-
drivers/iio/cdc/ad7150.c | 2 +-
drivers/iio/cdc/ad7746.c | 2 +-
drivers/iio/chemical/bme680_core.c | 2 +-
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 +-
29 files changed, 34 insertions(+), 34 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-07 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 10:46 Shi Hao [this message]
2026-03-07 10:47 ` [PATCH v2 1/6] iio: accel: fix spelling mistakes in comments 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
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=20260307104705.49129-1-i.shihao.999@gmail.com \
--to=i.shihao.999@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.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