devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sim manseop <semtax33@gmail.com>
To: devicetree@vger.kernel.org
Cc: robh@kernel.org, sim manseop <semtax33@gmail.com>
Subject: [PATCH v4 2/2] dt-bindings: i2c: Fix SMBus typo
Date: Thu, 13 Sep 2018 10:45:36 +0000	[thread overview]
Message-ID: <20180913104536.2375-1-semtax33@gmail.com> (raw)

Fix typo 'SMbus' to 'SMBus'

Signed-off-by: sim manseop <semtax33@gmail.com>

---
Changes in v4:
- modifing Signed-off-by name

---
Changes in v3:
- modifing subject

---
Changes in v2:
- modifing subject
- changed commit message
---
 Documentation/devicetree/bindings/i2c/i2c.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/i2c/i2c.txt b/Documentation/devicetree/bindings/i2c/i2c.txt
index 11263982470e..44efafdfd7f5 100644
--- a/Documentation/devicetree/bindings/i2c/i2c.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c.txt
@@ -84,7 +84,7 @@ Binding may contain optional "interrupts" property, describing interrupts
 used by the device. I2C core will assign "irq" interrupt (or the very first
 interrupt if not using interrupt names) as primary interrupt for the slave.
 
-Alternatively, devices supporting SMbus Host Notify, and connected to
+Alternatively, devices supporting SMBus Host Notify, and connected to
 adapters that support this feature, may use "host-notify" property. I2C
 core will create a virtual interrupt for Host Notify and assign it as
 primary interrupt for the slave.
-- 
2.17.1

             reply	other threads:[~2018-09-13 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 10:45 sim manseop [this message]
2018-09-26 21:03 ` [PATCH v4 2/2] dt-bindings: i2c: Fix SMBus typo 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=20180913104536.2375-1-semtax33@gmail.com \
    --to=semtax33@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --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).