From: patchwork-bot+linux-riscv@kernel.org
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
ryan.roberts@arm.com, alex@ghiti.fr, rafael@kernel.org,
catalin.marinas@arm.com, kernel@vger.kernel.org,
cuiyunhui@bytedance.com, linux-acpi@vger.kernel.org,
akpm@linux-foundation.org, lenb@kernel.org
Subject: Re: [PATCH 0/2] ACPI: support BGRT table on RISC-V
Date: Wed, 06 Aug 2025 17:15:50 +0000 [thread overview]
Message-ID: <175450055074.2863135.7748247249569837976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250729131535.522205-1-heinrich.schuchardt@canonical.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Tue, 29 Jul 2025 15:15:33 +0200 you wrote:
> The BGRT table is used to display a vendor logo in the boot process.
> There is no good reason why RISC-V should not support it.
>
> Remove the architecture constraint.
>
> Heinrich Schuchardt (2):
> RISC-V: ACPI: enable parsing the BGRT table
> ACPI: support BGRT table on RISC-V
>
> [...]
Here is the summary with links:
- [1/2] RISC-V: ACPI: enable parsing the BGRT table
https://git.kernel.org/riscv/c/1f768661a03e
- [2/2] ACPI: support BGRT table on RISC-V
https://git.kernel.org/riscv/c/bf2825bf00ad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-06 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 13:15 [PATCH 0/2] ACPI: support BGRT table on RISC-V Heinrich Schuchardt
2025-07-29 13:15 ` [PATCH 1/2] RISC-V: ACPI: enable parsing the BGRT table Heinrich Schuchardt
2025-07-29 13:15 ` [PATCH 2/2] ACPI: support BGRT table on RISC-V Heinrich Schuchardt
2025-07-31 13:13 ` Alexandre Ghiti
2025-07-31 18:17 ` Rafael J. Wysocki
2025-07-31 19:51 ` Alexandre Ghiti
2025-07-30 4:48 ` [PATCH 0/2] " Sunil V L
2025-08-06 17:15 ` 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=175450055074.2863135.7748247249569837976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=cuiyunhui@bytedance.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=kernel@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=ryan.roberts@arm.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