From: Hal Feng <hal.feng@starfivetech.com>
To: Conor Dooley <conor@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Emil Renner Berthing" <kernel@esmil.dk>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Walker Chen <walker.chen@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC
Date: Fri, 18 Aug 2023 20:40:42 +0800 [thread overview]
Message-ID: <e47c92c9-c57b-83b1-c444-0fce41164fe1@starfivetech.com> (raw)
In-Reply-To: <20230726-upriver-net-8490aa69df8a@spud>
On Wed, 26 Jul 2023 17:21:39 +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> On Mon, 24 Jul 2023 14:51:56 +0800, Walker Chen wrote:
>> These patches add dma and tdm nodes for the StarFive JH7110 SoC, they
>> are based on linux-next. I have tested them on the VisionFive2 board.
>> Thanks.
>>
>> Best regards,
>> Walker
>>
>> [...]
>
> Applied to riscv-dt-for-next, thanks!
>
> [1/2] riscv: dts: starfive: jh7110: add dma controller node
> https://git.kernel.org/conor/c/ac73c09716c3
> [2/2] riscv: dts: starfive: jh7110: add the node and pins configuration for tdm
> https://git.kernel.org/conor/c/e7c304c0346d
Hi, Conor,
You had deleted the `status = "okay";` of usb0 by mistake in this commit.
&usb0 {
dr_mode = "peripheral";
- status = "okay";
};
Could you please help fix it?
Best regards,
Hal
prev parent reply other threads:[~2023-08-18 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 6:51 [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC Walker Chen
2023-07-24 6:51 ` [PATCH v1 1/2] riscv: dts: starfive: jh7110: add dma controller node Walker Chen
2023-07-24 6:51 ` [PATCH v1 2/2] riscv: dts: starfive: jh7110: add the node and pins configuration for tdm Walker Chen
2023-07-26 16:21 ` [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC Conor Dooley
2023-08-18 12:40 ` Hal Feng [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=e47c92c9-c57b-83b1-c444-0fce41164fe1@starfivetech.com \
--to=hal.feng@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--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=robh+dt@kernel.org \
--cc=walker.chen@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).