From: Conor Dooley <conor@kernel.org>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Minda Chen <minda.chen@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [dt-for-next v1 0/2] Add USB PHY and USB dts node for JH7110
Date: Wed, 26 Jul 2023 17:15:19 +0100 [thread overview]
Message-ID: <20230726-disjoin-valiant-9eb92de6a240@spud> (raw)
In-Reply-To: <20230726100609.72550-1-minda.chen@starfivetech.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Wed, 26 Jul 2023 03:06:07 -0700, Minda Chen wrote:
> Add USB and USB/PCIe PHY dts node for StarFive JH7110. The PHY
> driver is in linux-phy-next tree.
>
> Minda Chen (2):
> riscv: dts: starfive: Add USB and PCIe PHY nodes for JH7110
> riscv: dts: starfive: Add USB dts node for JH7110
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/2] riscv: dts: starfive: Add USB and PCIe PHY nodes for JH7110
https://git.kernel.org/conor/c/c2a10081c033
[2/2] riscv: dts: starfive: Add USB dts node for JH7110
https://git.kernel.org/conor/c/e126aa3abc4e
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-26 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 10:06 [dt-for-next v1 0/2] Add USB PHY and USB dts node for JH7110 Minda Chen
2023-07-26 10:06 ` [dt-for-next v1 1/2] riscv: dts: starfive: Add USB and PCIe PHY nodes " Minda Chen
2023-07-26 10:06 ` [dt-for-next v1 2/2] riscv: dts: starfive: Add USB dts node " Minda Chen
2023-07-26 16:15 ` 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=20230726-disjoin-valiant-9eb92de6a240@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=minda.chen@starfivetech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.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