From: Rob Herring <robh@kernel.org>
To: Nik Bune <n2h9z4@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wim@linux-watchdog.org, stwiss.opensource@diasemi.com,
skhan@linuxfoundation.org, linux@roeck-us.net,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
linux-watchdog@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3] dt-bindings: watchdog: da9062-wdt: convert txt to yaml
Date: Wed, 25 Oct 2023 15:01:28 -0500 [thread overview]
Message-ID: <169826372027.1056631.8936616422863313473.robh@kernel.org> (raw)
In-Reply-To: <20231014170434.159310-1-n2h9z4@gmail.com>
On Sat, 14 Oct 2023 19:04:34 +0200, Nik Bune wrote:
> Convert txt file to yaml.
> Add a mainterner block. Took a value from dlg,da9063 PMIC.
>
>
> Signed-off-by: Nik Bune <n2h9z4@gmail.com>
> ---
>
> Changes in v3
> - Changed type of dlg,wdt-sd property from boolean to uint32. Following the discussed in v2 patch thread.
>
> v2 patch: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231010211439.98458-1-n2h9z4@gmail.com/
>
>
> .../bindings/watchdog/da9062-wdt.txt | 34 -------------
> .../watchdog/dlg,da9062-watchdog.yaml | 50 +++++++++++++++++++
> 2 files changed, 50 insertions(+), 34 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/da9062-wdt.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/dlg,da9062-watchdog.yaml
>
It seems watchdog bindings aren't getting applied, so I've applied it.
Wim, please take watchdog bindings in the future unless noted otherwise.
Rob
prev parent reply other threads:[~2023-10-25 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 17:04 [PATCH v3] dt-bindings: watchdog: da9062-wdt: convert txt to yaml Nik Bune
2023-10-15 9:29 ` Krzysztof Kozlowski
2023-10-15 12:28 ` Guenter Roeck
2023-10-25 20:01 ` Rob Herring [this message]
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=169826372027.1056631.8936616422863313473.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=n2h9z4@gmail.com \
--cc=robh+dt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stwiss.opensource@diasemi.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).