From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Chris Brandt <chris.brandt@renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/4] dt-bindings: i2c: renesas: Rename bindings documentation files
Date: Wed, 14 Aug 2019 15:04:22 +0200 [thread overview]
Message-ID: <20190814130422.GE9716@ninjato> (raw)
In-Reply-To: <20190809213004.31181-1-horms+renesas@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On Fri, Aug 09, 2019 at 02:30:00PM -0700, Simon Horman wrote:
> Rename the bindings documentation file for Renesas I2C controllers.
>
> This is part of an ongoing effort to name bindings documentation files for
> Renesas IP blocks consistently, in line with the compat strings they
> document.
>
> Based on v5.3-rc1
>
> Changes since v1
> * Accumulate review tags
> * Correct changelogs
>
> Simon Horman (4):
> dt-bindings: i2c: sh_mobile: Rename bindings documentation file
> dt-bindings: i2c: rcar: Rename bindings documentation file
> dt-bindings: i2c: riic: Rename bindings documentation file
> dt-bindings: i2c: i2c-emev2: Rename bindings documentation file
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-14 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 21:30 [PATCH v2 0/4] dt-bindings: i2c: renesas: Rename bindings documentation files Simon Horman
2019-08-09 21:30 ` [PATCH v2 1/4] dt-bindings: i2c: sh_mobile: Rename bindings documentation file Simon Horman
2019-08-09 21:30 ` [PATCH v2 2/4] dt-bindings: i2c: rcar: " Simon Horman
2019-08-09 21:30 ` [PATCH v2 3/4] dt-bindings: i2c: riic: " Simon Horman
2019-08-09 21:30 ` [PATCH v2 4/4] dt-bindings: i2c: i2c-emev2: " Simon Horman
2019-08-14 13:04 ` Wolfram Sang [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=20190814130422.GE9716@ninjato \
--to=wsa@the-dreams.de \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).