From: Rob Herring <robh@kernel.org>
To: sim manseop <semtax33@gmail.com>
Cc: devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: i2c: Fix SMBus typo
Date: Mon, 10 Sep 2018 14:58:38 -0500 [thread overview]
Message-ID: <20180910195838.GA14500@bogus> (raw)
In-Reply-To: <20180901094912.2403-1-semtax33@gmail.com>
On Sat, Sep 01, 2018 at 09:49:12AM +0000, sim manseop wrote:
> Fix typo 'SMbus' to 'SMBus'
>
> Signed-off-by: manseop sim <semtax33@gmail.com>
checkpatch.pl complains that author name and signoff don't match.
>
> ---
> 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
>
prev parent reply other threads:[~2018-09-10 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 9:49 [PATCH v3 2/2] dt-bindings: i2c: Fix SMBus typo sim manseop
2018-09-10 19:58 ` Rob Herring [this message]
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=20180910195838.GA14500@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=semtax33@gmail.com \
/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).