From: Pavel Machek <pavel@ucw.cz>
To: Lee Jones <lee.jones@linaro.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: [PATCH] mfd/ti-lmu: fix typo
Date: Thu, 27 Dec 2018 20:53:37 +0100 [thread overview]
Message-ID: <20181227195337.GA12008@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Fix typo in comment.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
diff --git a/include/linux/mfd/ti-lmu.h b/include/linux/mfd/ti-lmu.h
index 1ef51ed..06b2a9b 100644
--- a/include/linux/mfd/ti-lmu.h
+++ b/include/linux/mfd/ti-lmu.h
@@ -75,7 +75,7 @@ enum lm363x_regulator_id {
* struct ti_lmu
*
* @dev: Parent device pointer
- * @regmap: Used for i2c communcation on accessing registers
+ * @regmap: Used for i2c communication on accessing registers
* @en_gpio: GPIO for HWEN pin [Optional]
* @notifier: Notifier for reporting hwmon event
*/
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2018-12-27 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181227195337.GA12008@amd \
--to=pavel@ucw.cz \
--cc=lee.jones@linaro.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).