From: Johan Jonker <jbx6244@gmail.com>
To: robh+dt@kernel.org
Cc: mark.rutland@arm.com, ulf.hansson@linaro.org,
linux-mmc@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/2] dt-bindings: mmc: remove identical phrase in disable-wp text
Date: Sat, 28 Dec 2019 10:30:58 +0100 [thread overview]
Message-ID: <20191228093059.2817-1-jbx6244@gmail.com> (raw)
In-Reply-To: <20191219145843.3823-1-jbx6244@gmail.com>
There are two identical phrases in the disable-wp text,
so remove one of them.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
Documentation/devicetree/bindings/mmc/mmc-controller.yaml | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
index b130450c3..d668d0fbe 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
+++ b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
@@ -96,8 +96,7 @@ properties:
description:
When set, no physical write-protect line is present. This
property should only be specified when the controller has a
- dedicated write-protect detection logic. If a GPIO is always
- used for the write-protect detection. If a GPIO is always used
+ dedicated write-protect detection logic. If a GPIO is always used
for the write-protect detection logic, it is sufficient to not
specify the wp-gpios property in the absence of a write-protect
line.
--
2.11.0
next prev parent reply other threads:[~2019-12-28 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:58 [PATCH] dt-bindings: mmc: clarify disable-wp text Johan Jonker
2019-12-28 9:30 ` Johan Jonker [this message]
2019-12-28 9:30 ` [PATCH v2 2/2] " Johan Jonker
2020-01-04 21:55 ` Rob Herring
2020-01-04 21:55 ` [PATCH v2 1/2] dt-bindings: mmc: remove identical phrase in " Rob Herring
2020-01-16 11:16 ` Ulf Hansson
2020-01-16 17:18 ` Rob Herring
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=20191228093059.2817-1-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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