From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Yu Jiaoliang <yujiaoliang@vivo.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Marcelo Schmitt <marcelo.schmitt@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Matteo Martelli <matteomartelli3@gmail.com>,
Michal Simek <michal.simek@amd.com>,
Ivan Mikhaylov <fr0st61te@gmail.com>,
Mike Looijmans <mike.looijmans@topic.nl>,
Dan Carpenter <dan.carpenter@linaro.org>,
Nuno Sa <nuno.sa@analog.com>,
Richard Leitner <richard.leitner@linux.dev>,
Stephen Boyd <sboyd@kernel.org>,
Wadim Egorov <w.egorov@phytec.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] iio: adc: Fix typos in comments across various files
Date: Thu, 26 Sep 2024 10:19:40 +0200 [thread overview]
Message-ID: <20240926101940.22bbc3fe@booty> (raw)
In-Reply-To: <20240926034411.3482986-1-yujiaoliang@vivo.com>
Hello Yu,
On Thu, 26 Sep 2024 11:43:54 +0800
Yu Jiaoliang <yujiaoliang@vivo.com> wrote:
> This commit fixes several typographical errors in comments within
> the drivers/iio/adc directory. No functional changes are made.
I think it would be useful to add those typo patterns to
scripts/spelling.txt, so checkpatch.pl will check them, preventing the
same typos from happening in the future.
With that added (perhaps in a separate patch), looks good.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-09-26 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 3:43 [PATCH v1] iio: adc: Fix typos in comments across various files Yu Jiaoliang
2024-09-26 8:19 ` Luca Ceresoli [this message]
2024-09-26 9:03 ` Yu Jiaoliang
2024-09-28 17:15 ` Jonathan Cameron
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=20240926101940.22bbc3fe@booty \
--to=luca.ceresoli@bootlin.com \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.carpenter@linaro.org \
--cc=fr0st61te@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=matteomartelli3@gmail.com \
--cc=michal.simek@amd.com \
--cc=mike.looijmans@topic.nl \
--cc=nuno.sa@analog.com \
--cc=opensource.kernel@vivo.com \
--cc=richard.leitner@linux.dev \
--cc=sboyd@kernel.org \
--cc=w.egorov@phytec.de \
--cc=yujiaoliang@vivo.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