[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200424154103.10311-2-zhengdejin5@gmail.com>
Date: Fri, 24 Apr 2020 23:41:02 +0800
From: Dejin Zheng <zhengdejin5@...il.com>
To: linus.walleij@...aro.org, bgolaszewski@...libre.com,
linux-gpio@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Dejin Zheng <zhengdejin5@...il.com>,
Andy Shevchenko <andy.shevchenko@...il.com>
Subject: [PATCH v2 1/2] gpio: ftgpio010: Fix small typo
Fix a spelling typo in gpio-ftgpio010.c by codespell
s/desireable/desirable/
Cc: Andy Shevchenko <andy.shevchenko@...il.com>
Signed-off-by: Dejin Zheng <zhengdejin5@...il.com>
---
v1 -> v2:
- split patch v1 (only one patch) into patches for each driver
by Bartosz's suggestion. thanks Bartosz.
drivers/gpio/gpio-ftgpio010.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-ftgpio010.c b/drivers/gpio/gpio-ftgpio010.c
index fbddb1662428..4031164780f7 100644
--- a/drivers/gpio/gpio-ftgpio010.c
+++ b/drivers/gpio/gpio-ftgpio010.c
@@ -193,7 +193,7 @@ static int ftgpio_gpio_set_config(struct gpio_chip *gc, unsigned int offset,
if (val == deb_div) {
/*
* The debounce timer happens to already be set to the
- * desireable value, what a coincidence! We can just enable
+ * desirable value, what a coincidence! We can just enable
* debounce on this GPIO line and return. This happens more
* often than you think, for example when all GPIO keys
* on a system are requesting the same debounce interval.
--
2.25.0
Powered by blists - more mailing lists