From: Dejin Zheng <zhengdejin5@gmail.com>
To: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Dejin Zheng <zhengdejin5@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: [PATCH v2 2/2] gpio: mm-lantiq: Fix small typo
Date: Fri, 24 Apr 2020 23:41:03 +0800 [thread overview]
Message-ID: <20200424154103.10311-3-zhengdejin5@gmail.com> (raw)
In-Reply-To: <20200424154103.10311-1-zhengdejin5@gmail.com>
Fix a spelling typo in gpio-mm-lantiq.c by codespell
s/dont/don't/
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Dejin Zheng <zhengdejin5@gmail.com>
---
v1 -> v2:
- split patch v1 (only one patch) into patches for each driver
by Bartosz's suggestion. thanks Bartosz.
drivers/gpio/gpio-mm-lantiq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-mm-lantiq.c b/drivers/gpio/gpio-mm-lantiq.c
index f460d71b0c92..538e31fe8903 100644
--- a/drivers/gpio/gpio-mm-lantiq.c
+++ b/drivers/gpio/gpio-mm-lantiq.c
@@ -36,7 +36,7 @@ struct ltq_mm {
* @chip: Pointer to our private data structure.
*
* Write the shadow value to the EBU to set the gpios. We need to set the
- * global EBU lock to make sure that PCI/MTD dont break.
+ * global EBU lock to make sure that PCI/MTD don't break.
*/
static void ltq_mm_apply(struct ltq_mm *chip)
{
--
2.25.0
next prev parent reply other threads:[~2020-04-24 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:41 [PATCH v2 0/2] gpio: fix several typos Dejin Zheng
2020-04-24 15:41 ` [PATCH v2 1/2] gpio: ftgpio010: Fix small typo Dejin Zheng
2020-04-28 13:50 ` Linus Walleij
2020-04-24 15:41 ` Dejin Zheng [this message]
2020-04-28 13:53 ` [PATCH v2 2/2] gpio: mm-lantiq: " Linus Walleij
2020-04-28 15:30 ` Andy Shevchenko
2020-04-28 20:41 ` Linus Walleij
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=20200424154103.10311-3-zhengdejin5@gmail.com \
--to=zhengdejin5@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).