From: Rob Herring <robh@kernel.org>
To: l4stpr0gr4m@gmail.com
Cc: trivial@kernel.org, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nsaenzjulienne@suse.de,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] docs/devicetree/i2c: brcm,bcm2835: fix node id in example
Date: Mon, 18 May 2020 14:43:32 -0600 [thread overview]
Message-ID: <20200518204332.GA13919@bogus> (raw)
In-Reply-To: <1589140701-7516-1-git-send-email-l4stpr0gr4m@gmail.com>
On Mon, 11 May 2020 04:58:21 +0900, wrote:
> From: Kangmin Park <l4stpr0gr4m@gmail.com>
>
> This is a trivial patch to fix node id to match the reg in example.
>
> Signed-off-by: Kangmin Park <l4stpr0gr4m@gmail.com>
> ---
> Documentation/devicetree/bindings/i2c/brcm,bcm2835-i2c.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied, thanks!
prev parent reply other threads:[~2020-05-18 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 19:58 [PATCH] docs/devicetree/i2c: brcm,bcm2835: fix node id in example l4stpr0gr4m
2020-05-18 20:43 ` 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=20200518204332.GA13919@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=l4stpr0gr4m@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=trivial@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).