From: "Heiko Stübner" <heiko@sntech.de>
To: Shreeya Patel <shreeya.patel@collabora.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: wim@linux-watchdog.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jamie@jamieiles.com,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH 2/2] dt-bindings: watchdog: rockchip: Add rockchip,rk3588-wdt string
Date: Wed, 29 Mar 2023 15:04:52 +0200 [thread overview]
Message-ID: <4256207.ejJDZkT8p0@diego> (raw)
In-Reply-To: <157937fd-0af7-4ff5-8430-2f956c7aafba@roeck-us.net>
Hi Guenter,
Am Mittwoch, 29. März 2023, 14:47:34 CEST schrieb Guenter Roeck:
> On Wed, Mar 29, 2023 at 02:30:48AM +0530, Shreeya Patel wrote:
> > Add rockchip,rk3588-wdt compatible string.
> >
> > Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
just the usual question who is expected to pick up the binding patch?
Should I just take it together with the dts-patch or do we wait for
a watchdog-maintainer to pick up the binding alone?
Thanks
Heiko
next prev parent reply other threads:[~2023-03-29 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:00 [PATCH 0/2] RK3588 watchdog support Shreeya Patel
2023-03-28 21:00 ` [PATCH 1/2] arm64: dts: rockchip: Enable watchdog support for RK3588 Shreeya Patel
2023-03-28 21:00 ` [PATCH 2/2] dt-bindings: watchdog: rockchip: Add rockchip,rk3588-wdt string Shreeya Patel
2023-03-28 21:15 ` Heiko Stübner
2023-03-29 8:35 ` Krzysztof Kozlowski
2023-03-29 12:47 ` Guenter Roeck
2023-03-29 13:04 ` Heiko Stübner [this message]
2023-03-29 21:52 ` Guenter Roeck
2023-03-30 11:44 ` [PATCH 0/2] RK3588 watchdog support Heiko Stuebner
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=4256207.ejJDZkT8p0@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jamie@jamieiles.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.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