From: Rob Herring <robh@kernel.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: wim@linux-watchdog.org, krzysztof.kozlowski@canonical.com,
devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux@roeck-us.net, linux-kernel@vger.kernel.org,
robh+dt@kernel.org
Subject: Re: [PATCH v4] dt-bindings: watchdog: convert faraday,ftwdt010 to yaml
Date: Thu, 17 Feb 2022 17:32:41 -0600 [thread overview]
Message-ID: <Yg7bGU1A/GvtyN/z@robh.at.kernel.org> (raw)
In-Reply-To: <20220211115528.3382374-1-clabbe@baylibre.com>
On Fri, 11 Feb 2022 11:55:28 +0000, Corentin Labbe wrote:
> Converts watchdog/faraday,ftwdt010.txt to yaml.
> This permits to detect missing properties like clocks and resets or
> compatible like moxa,moxart-watchdog.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> ---
> Changes since v1:
> - Added myself as maintainer as requested by Linus
> - Added $ref to watchdog.yaml
> - Removed useless quotes
> - Added blank lines between properties
> - Removed timeout-secs as already provided by watchdog.yaml
>
> Change since v2:
> - rewrite compatible section
>
> Changes since v3:
> - Fix indent errors reported by yamllint
> - Change additionalProperties to unevaluatedProperties
> - Added timeout-secs in example
>
> .../bindings/watchdog/faraday,ftwdt010.txt | 22 ------
> .../bindings/watchdog/faraday,ftwdt010.yaml | 67 +++++++++++++++++++
> 2 files changed, 67 insertions(+), 22 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/faraday,ftwdt010.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/faraday,ftwdt010.yaml
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-18 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 11:55 [PATCH v4] dt-bindings: watchdog: convert faraday,ftwdt010 to yaml Corentin Labbe
2022-02-11 14:00 ` Krzysztof Kozlowski
2022-02-17 23:32 ` Rob Herring [this message]
2022-03-09 23:21 ` 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=Yg7bGU1A/GvtyN/z@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).