From: Rob Herring <robh@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
linux-gpio@vger.kernel.org, john@phrozen.org, robh+dt@kernel.org
Subject: Re: [PATCH v4] dt-bindings: gpio: stp: convert to json-schema
Date: Thu, 10 Jun 2021 11:27:15 -0500 [thread overview]
Message-ID: <20210610162715.GA1921873@robh.at.kernel.org> (raw)
In-Reply-To: <20210603135945.3495-1-olek2@wp.pl>
On Thu, 03 Jun 2021 15:59:45 +0200, Aleksander Jan Bajkowski wrote:
> Convert the Lantiq STP Device Tree binding documentation to json-schema.
> Add the missing pinctrl property to the example. Add missing lantiq,phy3
> and lantiq,phy4 bindings for xRX300 and xRX330 SoCs.
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Changes since v3:
> - Removed description of the reg property.
> - Changed regex pattern property.
> - Moved lantiq,rising to properties.
> Changes since v2:
> - Changed phy numbering in description of pattern Properties. Numbering
> should start with 1.
> Changes since v1:
> - Renamed node to gpio.
> - Dropped default pinctrl from this binding.
> - Converted lantiq,phyX to patternProperties.
> ---
> .../bindings/gpio/gpio-stp-xway.txt | 42 --------
> .../bindings/gpio/gpio-stp-xway.yaml | 99 +++++++++++++++++++
> 2 files changed, 99 insertions(+), 42 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-stp-xway.txt
> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-06-10 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 13:59 [PATCH v4] dt-bindings: gpio: stp: convert to json-schema Aleksander Jan Bajkowski
2021-06-10 16:27 ` Rob Herring [this message]
2021-06-25 10:28 ` Bartosz Golaszewski
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=20210610162715.GA1921873@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=robh+dt@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).