From: Rob Herring <robh@kernel.org>
To: Nik Bune <n2h9z4@gmail.com>
Cc: linux-watchdog@vger.kernel.org, wim@linux-watchdog.org,
robh+dt@kernel.org, conor+dt@kernel.org, baruch@tkos.co.il,
linux@roeck-us.net, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, skhan@linuxfoundation.org
Subject: Re: [PATCH v2] dt-bindings: watchdog: cnxt,cx92755-wdt: convert txt to yaml
Date: Wed, 25 Oct 2023 15:01:53 -0500 [thread overview]
Message-ID: <169826378704.1058225.17608945704305055668.robh@kernel.org> (raw)
In-Reply-To: <20231023202622.18558-1-n2h9z4@gmail.com>
On Mon, 23 Oct 2023 22:26:22 +0200, Nik Bune wrote:
> Convert txt file to yaml.
> Add maintainers list.
>
> Signed-off-by: Nik Bune <n2h9z4@gmail.com>
> ---
>
> Changes in v2 (according to review comments):
> - Updated clocks property to have only maxItems without $ref and description.
> - Removed timeout-sec explicit definition, as it is defined in watchdog.yaml.
>
> v1 patch: https://lore.kernel.org/all/20231022120328.137788-1-n2h9z4@gmail.com/
>
> .../bindings/watchdog/cnxt,cx92755-wdt.yaml | 45 +++++++++++++++++++
> .../bindings/watchdog/digicolor-wdt.txt | 25 -----------
> 2 files changed, 45 insertions(+), 25 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/watchdog/cnxt,cx92755-wdt.yaml
> delete mode 100644 Documentation/devicetree/bindings/watchdog/digicolor-wdt.txt
>
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:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 20:26 Nik Bune
2023-10-24 7:39 ` Krzysztof Kozlowski
2023-10-24 18:05 ` 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=169826378704.1058225.17608945704305055668.robh@kernel.org \
--to=robh@kernel.org \
--cc=baruch@tkos.co.il \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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=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
all inboxes | Powered by JetHome®