From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Timothy Pearson <tpearson@raptorengineering.com>
Subject: Re: [PATCH 3/3] dt-bindings: mfd: rohm,bd96801-pmic: Correct timeout-sec length and reference watchdog schema
Date: Thu, 23 Oct 2025 08:41:42 +0300 [thread overview]
Message-ID: <e215a74f-4c66-4e8e-bb10-b90d782de2bf@gmail.com> (raw)
In-Reply-To: <20251020-dt-bindings-watchdog-timeout-v1-3-d0f3235eb327@linaro.org>
Thanks Krzysztof!
On 20/10/2025 19:52, Krzysztof Kozlowski wrote:
> The parent node of ROHM BD96801 PMIC is also holding properties for the
> watchdog, thus it should reference watchdog.yaml schema. OTOH, the
> timeout-sec property is used only as one number.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Acked-by: Matti Vaittinen <mazziesaccount@gmail.com>
next prev parent reply other threads:[~2025-10-23 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 16:52 [PATCH 0/3] mfd/watchdog: dt-bindings: Reference watchdog schema in rohm,bd96801-pmic Krzysztof Kozlowski
2025-10-20 16:52 ` [PATCH 1/3] dt-bindings: watchdog: Restrict timeout-sec to one number Krzysztof Kozlowski
2025-10-20 18:27 ` Guenter Roeck
2025-10-26 21:32 ` Rob Herring (Arm)
2025-10-20 16:52 ` [PATCH 2/3] dt-bindings: watchdog: Allow node names named 'pmic' Krzysztof Kozlowski
2025-10-20 18:28 ` Guenter Roeck
2025-10-26 21:33 ` Rob Herring (Arm)
2025-10-20 16:52 ` [PATCH 3/3] dt-bindings: mfd: rohm,bd96801-pmic: Correct timeout-sec length and reference watchdog schema Krzysztof Kozlowski
2025-10-20 18:29 ` Guenter Roeck
2025-10-23 5:41 ` Matti Vaittinen [this message]
2025-10-26 21:37 ` Rob Herring (Arm)
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=e215a74f-4c66-4e8e-bb10-b90d782de2bf@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=tpearson@raptorengineering.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 NNTP newsgroup(s).