From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Stanimir Varbanov <svarbanov@suse.de>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>, Lee Jones <lee@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Willow Cunningham <willow.e.cunningham@gmail.com>,
Stefan Wahren <wahrenst@gmx.net>,
Saenz Julienne <nsaenz@kernel.org>,
Andrea della Porta <andrea.porta@suse.com>,
Phil Elwell <phil@raspberrypi.com>,
Jonathan Bell <jonathan@raspberrypi.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: Re: [PATCH v3 4/4] arm64: dts: broadcom: bcm2712: Add watchdog DT node
Date: Tue, 16 Dec 2025 15:59:04 -0800 [thread overview]
Message-ID: <351d9321-e5e9-43cd-bd74-68aef80aa177@broadcom.com> (raw)
In-Reply-To: <189702e0-e6f0-44c5-bed6-eef058d90b76@suse.de>
On 12/16/25 05:00, Stanimir Varbanov wrote:
> Hi Florian,
>
> On 11/5/25 6:55 PM, Florian Fainelli wrote:
>> From: Florian Fainelli <f.fainelli@gmail.com>
>>
>> On Fri, 31 Oct 2025 20:33:09 +0200, Stanimir Varbanov <svarbanov@suse.de> wrote:
>>> Add watchdog device-tree node for bcm2712 SoC.
>>>
>>> Signed-off-by: Stanimir Varbanov <svarbanov@suse.de>
>>> ---
>>
>> Applied to https://github.com/Broadcom/stblinux/commits/devicetree-arm64/next, thanks!
>
> For some reason this is not part of v6.19-rc1.
I did not send out the pull request, sorry about that. Let's see if the
SoC maintainers can still take it, if not that will be v6.20 material.
--
Florian
next prev parent reply other threads:[~2025-12-16 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 18:33 [PATCH v3 0/4] Add watchdog support for bcm2712 Stanimir Varbanov
2025-10-31 18:33 ` [PATCH v3 1/4] pmdomain: bcm: bcm2835-power: Prepare to support BCM2712 Stanimir Varbanov
2025-10-31 18:33 ` [PATCH v3 2/4] dt-bindings: soc: bcm: Add bcm2712 compatible Stanimir Varbanov
2025-11-04 17:34 ` Conor Dooley
2025-10-31 18:33 ` [PATCH v3 3/4] mfd: bcm2835-pm: Add support for BCM2712 Stanimir Varbanov
2025-10-31 18:33 ` [PATCH v3 4/4] arm64: dts: broadcom: bcm2712: Add watchdog DT node Stanimir Varbanov
2025-11-05 16:55 ` Florian Fainelli
2025-12-16 13:00 ` Stanimir Varbanov
2025-12-16 23:59 ` Florian Fainelli [this message]
2025-11-05 12:52 ` [PATCH v3 0/4] Add watchdog support for bcm2712 Ulf Hansson
2025-11-05 13:41 ` Stanimir Varbanov
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=351d9321-e5e9-43cd-bd74-68aef80aa177@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrea.porta@suse.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathan@raspberrypi.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=svarbanov@suse.de \
--cc=ulf.hansson@linaro.org \
--cc=wahrenst@gmx.net \
--cc=willow.e.cunningham@gmail.com \
/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).