From: Heiko Stuebner <heiko@sntech.de>
To: Fabio Estevam <festevam@gmail.com>, Guenter Roeck <linux@roeck-us.net>
Cc: wim@linux-watchdog.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@nabladev.com>
Subject: Re: [PATCH v2] dt-bindings: watchdog: rockchip: Add RV1103B compatible
Date: Thu, 07 May 2026 13:22:13 +0200 [thread overview]
Message-ID: <5466403.V25eIC5XRa@phil> (raw)
In-Reply-To: <066e3058-5ba8-4695-9f45-523c7d43ab76@roeck-us.net>
Am Freitag, 10. April 2026, 17:49:55 Mitteleuropäische Sommerzeit schrieb Guenter Roeck:
> On 4/8/26 03:28, Fabio Estevam wrote:
> > Hi Guenter,
> >
> > On Mon, Mar 16, 2026 at 11:14 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >>
> >> On 3/9/26 17:20, Fabio Estevam wrote:
> >>> From: Fabio Estevam <festevam@nabladev.com>
> >>>
> >>> The RV1103B watchdog is compatible with the existing DesignWare Watchdog
> >>> binding. Add the rockchip,rv1103b-wdt compatible string.
> >>>
> >>> Signed-off-by: Fabio Estevam <festevam@nabladev.com>
> >>
> >> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> >
> > Could you please apply this one?
>
> Wim applies watchdog subsystem patches.
seems to have changed, as it was applied as
https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?h=watchdog-next&id=882fc25d868fbd0d71751df4df49c4b55e3fa230
@Fabio, I guess you can send that rv1103b watchdog devicetree
node now.
Heiko
next prev parent reply other threads:[~2026-05-07 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 0:20 [PATCH v2] dt-bindings: watchdog: rockchip: Add RV1103B compatible Fabio Estevam
2026-03-10 8:10 ` Heiko Stuebner
2026-03-11 8:19 ` Krzysztof Kozlowski
2026-03-16 14:14 ` Guenter Roeck
2026-04-08 10:28 ` Fabio Estevam
2026-04-10 15:49 ` Guenter Roeck
2026-05-07 11:22 ` Heiko Stuebner [this message]
2026-05-07 11:33 ` Fabio Estevam
2026-05-07 13:44 ` Guenter Roeck
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=5466403.V25eIC5XRa@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.