From: Dan Murphy <dmurphy@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>, <robh@kernel.org>,
<marek.behun@nic.cz>
Cc: <devicetree@vger.kernel.org>, <linux-leds@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH] leds: multicolor: Fix camel case in documentation
Date: Mon, 20 Jul 2020 14:05:47 -0500 [thread overview]
Message-ID: <20200720190547.4735-1-dmurphy@ti.com> (raw)
Fix the camel case of MultiColor to Multicolor.
Fixes: f5a6eb5c5e38 ("leds: multicolor: Introduce a multicolor class definition")
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
Documentation/leds/leds-class-multicolor.rst | 2 +-
drivers/leds/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/leds/leds-class-multicolor.rst b/Documentation/leds/leds-class-multicolor.rst
index 6204f391fd40..c57b98bfd387 100644
--- a/Documentation/leds/leds-class-multicolor.rst
+++ b/Documentation/leds/leds-class-multicolor.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: GPL-2.0
====================================
-MultiColor LED handling under Linux
+Multicolor LED handling under Linux
====================================
Description
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index a2c72212ddfc..1de6e8e264a0 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -31,7 +31,7 @@ config LEDS_CLASS_FLASH
as a module.
config LEDS_CLASS_MULTICOLOR
- tristate "LED MultiColor Class Support"
+ tristate "LED Multicolor Class Support"
depends on LEDS_CLASS
help
This option enables the multicolor LED sysfs class in /sys/class/leds.
--
2.27.0
next reply other threads:[~2020-07-20 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:05 Dan Murphy [this message]
2020-07-21 20:52 ` [PATCH] leds: multicolor: Fix camel case in documentation Pavel Machek
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=20200720190547.4735-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=pavel@ucw.cz \
--cc=robh@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).