From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: wim@linux-watchdog.org
Cc: linux@roeck-us.net, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, S32@nxp.com,
ghennadi.procopciuc@nxp.com, thomas.fossati@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, alexandru-catalin.ionita@nxp.com
Subject: Re: [PATCH v4 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer
Date: Thu, 24 Apr 2025 16:12:01 +0200 [thread overview]
Message-ID: <d06f9e32-0c53-4ec0-8e78-1eedf5d6e2fc@linaro.org> (raw)
In-Reply-To: <20250410082616.1855860-2-daniel.lezcano@linaro.org>
Hi Wim,
On 10/04/2025 10:26, 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>
> ---
I do believe all the comments have been taken into account, the driver
has been reviewed and tested.
Is it possible to merge those changes in order to have them available in
linux-next ?
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-04-24 14:12 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)
2025-04-12 3:23 ` Guenter Roeck
2025-04-24 14:12 ` Daniel Lezcano [this message]
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=d06f9e32-0c53-4ec0-8e78-1eedf5d6e2fc@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=S32@nxp.com \
--cc=alexandru-catalin.ionita@nxp.com \
--cc=conor+dt@kernel.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=robh@kernel.org \
--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®