From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor@kernel.org>,
Xingyu Wu <xingyu.wu@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Add watchdog nodes in StarFive JH7100/JH7110 DTS
Date: Mon, 15 May 2023 17:46:33 +0100 [thread overview]
Message-ID: <20230515-tribesman-sloppily-658f86d776ac@spud> (raw)
In-Reply-To: <20230509151723.84989-1-xingyu.wu@starfivetech.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Tue, 09 May 2023 23:17:21 +0800, Xingyu Wu wrote:
> and JH7110 SoCs. Patch 1 adds the node in JH7100 dts and Patch 2 adds it
> in JH7110 dts. This patch serises are based on Linux 6.4-rc1.
>
> Xingyu Wu (2):
> riscv: dts: starfive: jh7100: Add watchdog node
> riscv: dts: starfive: jh7110: Add watchdog node
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/2] riscv: dts: starfive: jh7100: Add watchdog node
https://git.kernel.org/conor/c/435ac3fbfbc6
[2/2] riscv: dts: starfive: jh7110: Add watchdog node
https://git.kernel.org/conor/c/6361b7de262a
Thanks,
Conor.
prev parent reply other threads:[~2023-05-15 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 15:17 [PATCH v1 0/2] Add watchdog nodes in StarFive JH7100/JH7110 DTS Xingyu Wu
2023-05-09 15:17 ` [PATCH v1 1/2] riscv: dts: starfive: jh7100: Add watchdog node Xingyu Wu
2023-05-09 15:17 ` [PATCH v1 2/2] riscv: dts: starfive: jh7110: " Xingyu Wu
2023-05-12 22:27 ` Conor Dooley
2023-05-15 1:47 ` Walker Chen
2023-05-15 7:22 ` Conor Dooley
2023-05-15 7:35 ` Walker Chen
2023-05-15 16:46 ` Conor Dooley [this message]
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=20230515-tribesman-sloppily-658f86d776ac@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=xingyu.wu@starfivetech.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).