From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, linux-riscv@lists.indradead.org,
conor@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, wens@csie.org, jernej.skrabec@gmail.com,
samuel@sholland.org, daire.mcnamara@microchip.com,
geert+renesas@glider.be, magnus.damm@gmail.com, kernel@esmil.dk,
jszhang@kernel.org, guoren@kernel.org, wefu@redhat.com,
unicorn_wang@outlook.com, devicetree@vger.kernel.org,
linux-sunxi@lists.linux.dev, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 0/6] riscv,isa-extensions additions
Date: Sun, 12 Nov 2023 00:55:46 +0000 [thread overview]
Message-ID: <169975054620.11360.8786420869587397898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231009-approve-verbalize-ce9324858e76@wendy>
Hello:
This series was applied to riscv/linux.git (fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 9 Oct 2023 10:37:44 +0100 you wrote:
> Now with the RFC tag dropped. There are no changes here from "RFC v2",
> other than the addition of tags that were provided along the way. I have
> not added "Zfh" to the T-Head based stuff, as I can't actually read the
> documentation that would show that they're encoding-for-encoding
> compatible with the standard extension, since it is apparently only in
> Chinese.
>
> [...]
Here is the summary with links:
- [v3,1/6] riscv: dts: microchip: convert isa detection to new properties
(no matching commit)
- [v3,2/6] riscv: dts: sifive: convert isa detection to new properties
(no matching commit)
- [v3,3/6] riscv: dts: starfive: convert isa detection to new properties
(no matching commit)
- [v3,4/6] riscv: dts: renesas: convert isa detection to new properties
(no matching commit)
- [v3,5/6] riscv: dts: allwinner: convert isa detection to new properties
https://git.kernel.org/riscv/c/c3f7c14856eb
- [v3,6/6] riscv: dts: thead: convert isa detection to new properties
https://git.kernel.org/riscv/c/0804f3bec9e9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-11-12 0:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 9:37 [PATCH v3 0/6] riscv,isa-extensions additions Conor Dooley
2023-10-09 9:37 ` [PATCH v3 1/6] riscv: dts: microchip: convert isa detection to new properties Conor Dooley
2023-10-09 9:37 ` [PATCH v3 2/6] riscv: dts: sifive: " Conor Dooley
2023-10-09 9:37 ` [PATCH v3 3/6] riscv: dts: starfive: " Conor Dooley
2023-10-09 9:37 ` [PATCH v3 4/6] riscv: dts: renesas: " Conor Dooley
2023-10-09 12:15 ` Geert Uytterhoeven
2023-10-09 16:16 ` Conor Dooley
2023-10-16 6:09 ` Yu-Chien Peter Lin
2023-10-16 7:17 ` Geert Uytterhoeven
2023-10-09 9:37 ` [PATCH v3 5/6] riscv: dts: allwinner: " Conor Dooley
2023-10-13 19:22 ` Jernej Škrabec
2023-10-09 9:37 ` [PATCH v3 6/6] riscv: dts: thead: " Conor Dooley
2023-10-15 12:22 ` (subset) [PATCH v3 0/6] riscv,isa-extensions additions Conor Dooley
2023-10-16 7:23 ` Geert Uytterhoeven
2023-10-16 8:09 ` Conor Dooley
2023-11-12 0:55 ` patchwork-bot+linux-riscv [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=169975054620.11360.8786420869587397898.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=jszhang@kernel.org \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.indradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=magnus.damm@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=unicorn_wang@outlook.com \
--cc=wefu@redhat.com \
--cc=wens@csie.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