From: Rob Herring <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-watchdog@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: watchdog: gpio: Convert bindings to YAML
Date: Fri, 4 Nov 2022 16:57:08 -0500 [thread overview]
Message-ID: <166759902739.2897037.49149114982975908.robh@kernel.org> (raw)
In-Reply-To: <20221102220530.147997-1-marex@denx.de>
On Wed, 02 Nov 2022 23:05:30 +0100, Marek Vasut wrote:
> Convert the gpio-wdt bindings from text to YAML ones, to permit DT validation.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
> Cc: linux-watchdog@vger.kernel.org
> To: devicetree@vger.kernel.org
> ---
> V2: - Add missing required: properties
> - Drop quotes around ref: referenced schema file name
> ---
> NOTE: The Maintainer entry should likely be changed, although it seems
> like this driver and its matching bindings are now unmaintained.
> ---
> .../devicetree/bindings/watchdog/gpio-wdt.txt | 28 -----------
> .../bindings/watchdog/linux,wdt-gpio.yaml | 47 +++++++++++++++++++
> 2 files changed, 47 insertions(+), 28 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/linux,wdt-gpio.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-11-04 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:05 [PATCH v2] dt-bindings: watchdog: gpio: Convert bindings to YAML Marek Vasut
2022-11-04 21:57 ` Rob Herring [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-03 1:22 Guenter Roeck
2022-11-03 16:31 ` Marek Vasut
2022-11-03 17:20 ` Guenter Roeck
2022-11-03 17:29 ` Marek Vasut
2022-11-03 1:27 Guenter Roeck
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=166759902739.2897037.49149114982975908.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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).