From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 2/5] dt-bindings: gpio: rcar: Add gpio-reserved-ranges support
Date: Tue, 7 Aug 2018 11:43:49 -0600 [thread overview]
Message-ID: <20180807174349.GA10321@rob-hp-laptop> (raw)
In-Reply-To: <1533628626-26503-3-git-send-email-biju.das@bp.renesas.com>
On Tue, Aug 07, 2018 at 08:57:03AM +0100, Biju Das wrote:
> Update the DT bindings documentation with the optional gpio-reserved-ranges
> properties.
>
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> Reviewed-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> ---
> V2 --> V3
> * Incorporated review comments.
> ---
> .../devicetree/bindings/gpio/renesas,gpio-rcar.txt | 61 +++++++++++++---------
> 1 file changed, 35 insertions(+), 26 deletions(-)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-08-07 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 7:57 [PATCH v3 0/5] Add GPIO and EAVB Pinctrl support Biju Das
2018-08-07 7:57 ` [PATCH v3 2/5] dt-bindings: gpio: rcar: Add gpio-reserved-ranges support Biju Das
2018-08-07 8:18 ` Geert Uytterhoeven
2018-08-07 17:43 ` Rob Herring [this message]
2018-08-29 8:48 ` Linus Walleij
2018-08-07 7:57 ` [PATCH v3 3/5] ARM: dts: r8a77470: Add GPIO support Biju Das
2018-08-10 12:10 ` Simon Horman
2018-08-07 7:57 ` [PATCH v3 4/5] ARM: dts: iwg23s-sbc: specify EtherAVB PHY IRQ Biju Das
2018-08-10 12:11 ` Simon Horman
2018-08-07 7:57 ` [PATCH v3 5/5] ARM: dts: iwg23s-sbc: Add pinctl support for EtherAVB Biju Das
2018-08-10 12:12 ` Simon Horman
2018-08-10 13:47 ` Biju Das
2018-08-17 8:44 ` Simon Horman
2018-08-17 9:03 ` Biju Das
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=20180807174349.GA10321@rob-hp-laptop \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.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