From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Igor Mammedov <imammedo@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Andrew Jones <ajones@ventanamicro.com>,
Anup Patel <anup@brainfault.org>,
Atish Kumar Patra <atishp@rivosinc.com>
Subject: Re: [PATCH 0/3] RISC-V: ACPI: Update FADT and MADT versions
Date: Thu, 24 Jul 2025 03:45:47 -0400 [thread overview]
Message-ID: <20250724034501-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250716144140.3954431-1-sunilvl@ventanamicro.com>
On Wed, Jul 16, 2025 at 08:11:37PM +0530, Sunil V L wrote:
> Since RISC-V support is added only in ACPI 6.6, it should adhere to the
> expected FADT and MADT versions. Update them.
Seems legit
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Risc maintainers, any feedback?
> Sunil V L (3):
> bios-tables-test-allowed-diff.h: Allow RISC-V FADT and MADT changes
> hw/riscv/virt-acpi-build.c: Update FADT and MADT versions
> tests/data/acpi/riscv64: Update expected FADT and MADT
>
> hw/riscv/virt-acpi-build.c | 4 ++--
> tests/data/acpi/riscv64/virt/APIC | Bin 116 -> 116 bytes
> tests/data/acpi/riscv64/virt/FACP | Bin 276 -> 276 bytes
> 3 files changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.43.0
prev parent reply other threads:[~2025-07-24 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 14:41 [PATCH 0/3] RISC-V: ACPI: Update FADT and MADT versions Sunil V L
2025-07-16 14:41 ` [PATCH 1/3] bios-tables-test-allowed-diff.h: Allow RISC-V FADT and MADT changes Sunil V L
2025-07-16 14:41 ` [PATCH 2/3] hw/riscv/virt-acpi-build.c: Update FADT and MADT versions Sunil V L
2025-07-16 16:34 ` Michael S. Tsirkin
2025-07-16 14:41 ` [PATCH 3/3] tests/data/acpi/riscv64: Update expected FADT and MADT Sunil V L
2025-07-24 7:45 ` Michael S. Tsirkin [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=20250724034501-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=anisinha@redhat.com \
--cc=anup@brainfault.org \
--cc=atishp@rivosinc.com \
--cc=dbarboza@ventanamicro.com \
--cc=imammedo@redhat.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.