From: "Rob Herring (Arm)" <robh@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-watchdog@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, alexandru-catalin.ionita@nxp.com,
linux@roeck-us.net, krzk+dt@kernel.org,
ghennadi.procopciuc@nxp.com, S32@nxp.com,
linux-kernel@vger.kernel.org, thomas.fossati@linaro.org,
wim@linux-watchdog.org
Subject: Re: [PATCH v4 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer
Date: Fri, 11 Apr 2025 11:27:27 -0500 [thread overview]
Message-ID: <174438884676.3345035.7521977412397143761.robh@kernel.org> (raw)
In-Reply-To: <20250410082616.1855860-2-daniel.lezcano@linaro.org>
On Thu, 10 Apr 2025 10:26:13 +0200, Daniel Lezcano wrote:
> Describe the Software Watchdog Timer available on the S32G platforms.
>
> Cc: Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
> Cc: Thomas Fossati <thomas.fossati@linaro.org>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> .../bindings/watchdog/nxp,s32g2-swt.yaml | 54 +++++++++++++++++++
> 1 file changed, 54 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/nxp,s32g2-swt.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-04-11 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:26 [PATCH v4 0/2] Add the NXP S32 Watchdog Daniel Lezcano
2025-04-10 8:26 ` [PATCH v4 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer Daniel Lezcano
2025-04-11 16:27 ` Rob Herring (Arm) [this message]
2025-04-12 3:23 ` Guenter Roeck
2025-04-24 14:12 ` Daniel Lezcano
2025-04-10 8:26 ` [PATCH v4 2/2] watchdog: Add the Watchdog Timer for the NXP S32 platform Daniel Lezcano
2025-04-12 3:22 ` Guenter Roeck
2025-04-14 9:07 ` Alexandru-Catalin Ionita
2025-05-14 15:30 ` [PATCH v4 0/2] Add the NXP S32 Watchdog Daniel Lezcano
2025-05-14 18:09 ` Guenter Roeck
2025-05-28 13:17 ` Daniel Lezcano
2025-05-28 19:24 ` Wim Van Sebroeck
2025-05-29 17:56 ` Daniel Lezcano
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=174438884676.3345035.7521977412397143761.robh@kernel.org \
--to=robh@kernel.org \
--cc=S32@nxp.com \
--cc=alexandru-catalin.ionita@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=thomas.fossati@linaro.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®