From: Alistair Francis <alistair23@gmail.com>
To: "Christoph Müllner" <christoph.muellner@vrull.eu>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Richard Henderson <richard.henderson@linaro.org>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Andrew Jones <ajones@ventanamicro.com>
Subject: Re: [PATCH 0/2] linux-user/riscv: Sync hwprobe keys with kernel
Date: Thu, 15 Feb 2024 19:54:28 +1000 [thread overview]
Message-ID: <CAKmqyKOxUjc-C_hUptj2gy7XzgYWzy6OL5cE_JXCLVPh_26Rhw@mail.gmail.com> (raw)
In-Reply-To: <20240207115926.887816-1-christoph.muellner@vrull.eu>
On Wed, Feb 7, 2024 at 10:00 PM Christoph Müllner
<christoph.muellner@vrull.eu> wrote:
>
> This series syncs the hwprobe keys with those available in the upstream
> kernel repository with the exception of Ztso, which is not supported in
> QEMU as of now.
>
> The first patch is a resend (sent on Nov 27), as it should have been
> picked up on Dec 6, but seems to got lost.
>
> Christoph Müllner (2):
> linux-user/riscv: Add Zicboz extensions to hwprobe
> linux-user/riscv: Sync hwprobe keys with Linux
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> linux-user/syscall.c | 99 +++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 93 insertions(+), 6 deletions(-)
>
> --
> 2.43.0
>
>
prev parent reply other threads:[~2024-02-15 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:59 [PATCH 0/2] linux-user/riscv: Sync hwprobe keys with kernel Christoph Müllner
2024-02-07 11:59 ` [PATCH 1/2] linux-user/riscv: Add Zicboz extensions to hwprobe Christoph Müllner
2024-02-14 13:26 ` Daniel Henrique Barboza
2024-02-07 11:59 ` [PATCH 2/2] linux-user/riscv: Sync hwprobe keys with Linux Christoph Müllner
2024-02-14 13:26 ` Daniel Henrique Barboza
2024-03-08 4:22 ` Alistair Francis
2024-03-08 13:15 ` Christoph Müllner
2024-02-15 9:54 ` Alistair Francis [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=CAKmqyKOxUjc-C_hUptj2gy7XzgYWzy6OL5cE_JXCLVPh_26Rhw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=christoph.muellner@vrull.eu \
--cc=dbarboza@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).