From: jacopo <jacopo@jmondi.org>
To: Rob Herring <robh@kernel.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
geert+renesas@glider.be, laurent.pinchart@ideasonboard.com,
chris.brandt@renesas.com, linus.walleij@linaro.org,
mark.rutland@arm.com, linux@armlinux.org.uk,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/7] dt-bindings: pinctrl: Add RZ/A1 bindings doc
Date: Fri, 31 Mar 2017 11:52:09 +0200 [thread overview]
Message-ID: <20170331095209.GG7900@w540> (raw)
In-Reply-To: <20170330223903.yafbhrdulrnv2pfz@rob-hp-laptop>
Hi Rob,
thanks for the ack
On Thu, Mar 30, 2017 at 05:39:03PM -0500, Rob Herring wrote:
> On Fri, Mar 24, 2017 at 04:22:09PM +0100, Jacopo Mondi wrote:
> > Add device tree bindings documentation for Renesas RZ/A1 gpio and pin
> > controller.
> >
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> > ---
> > .../bindings/pinctrl/renesas,rza1-pinctrl.txt | 143 +++++++++++++++++++++
> > 1 file changed, 143 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rza1-pinctrl.txt
>
> Acked-by: Rob Herring <robh@kernel.org>
Just an heads-up: in v4 dt bindings will change considerably to meet a
format more close to standard pin controller bindings.
I cannot take you ack here and apply to next iteration as it will
require you or other dt guardians to have a look at it again. Sorry
about this.
Thanks
j
next prev parent reply other threads:[~2017-03-31 9:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 15:22 [PATCH v3 0/8] Renesas RZ/A1 pin and gpio controller Jacopo Mondi
2017-03-24 15:22 ` [PATCH v3 1/7] pinctrl: " Jacopo Mondi
2017-03-24 15:42 ` Linus Walleij
2017-03-24 16:45 ` jacopo
2017-03-29 1:43 ` Linus Walleij
2017-03-29 7:30 ` Geert Uytterhoeven
2017-03-29 10:03 ` Linus Walleij
2017-03-24 15:22 ` [PATCH v3 2/7] dt-bindings: pinctrl: Add RZ/A1 bindings doc Jacopo Mondi
2017-03-30 22:39 ` Rob Herring
2017-03-31 9:52 ` jacopo [this message]
2017-03-24 15:22 ` [PATCH v3 3/7] arm: dts: dt-bindings: Add Renesas RZ pinctrl header Jacopo Mondi
2017-03-29 13:22 ` Linus Walleij
2017-03-29 14:55 ` Chris Brandt
2017-03-29 14:59 ` Geert Uytterhoeven
2017-03-29 15:18 ` Chris Brandt
2017-03-29 15:39 ` Chris Brandt
2017-03-30 8:15 ` Linus Walleij
2017-03-30 13:27 ` Chris Brandt
2017-03-29 15:56 ` jacopo
2017-03-30 8:33 ` Linus Walleij
2017-03-24 15:22 ` [PATCH v3 4/7] arm: dts: r7s72100: Add pin controller node Jacopo Mondi
2017-03-24 15:32 ` Sergei Shtylyov
2017-03-27 17:12 ` Chris Brandt
2017-03-29 13:26 ` jacopo
2017-03-24 15:22 ` [PATCH v3 5/7] arm: dts: genmai: Add SCIF2 pin group Jacopo Mondi
2017-03-24 15:22 ` [PATCH v3 6/7] arm: dts: genmai: Add RIIC2 " Jacopo Mondi
2017-03-24 15:22 ` [PATCH v3 7/7] arm: dts: genmai: Add user led device nodes Jacopo Mondi
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=20170331095209.GG7900@w540 \
--to=jacopo@jmondi.org \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--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