Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: "Clément Léger" <cleger@rivosinc.com>
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	 Andrew Jones <ajones@ventanamicro.com>,
	Anup Patel <apatel@ventanamicro.com>,
	 Atish Patra <atishp@rivosinc.com>
Subject: Re: [kvm-unit-tests PATCH v4 5/5] riscv: sbi: Add SSE extension tests
Date: Mon, 13 Jan 2025 18:22:41 +0100	[thread overview]
Message-ID: <20250113-5f909e9cad611aa6b69c52fc@orel> (raw)
In-Reply-To: <20250108-162405687be625303572c303@orel>


I still haven't finished the review, I just hit send instead of
save-as-draft by mistake :-) However, sending now for you to take a look
at what I have so for in parallel with me finishing the review also makes
sense.

Thanks,
drew

  reply	other threads:[~2025-01-13 17:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 16:21 [kvm-unit-tests PATCH v4 0/5] riscv: add SBI SSE extension tests Clément Léger
2024-11-25 16:21 ` [kvm-unit-tests PATCH v4 1/5] kbuild: allow multiple asm-offsets file to be generated Clément Léger
2025-01-07 17:14   ` Andrew Jones
2024-11-25 16:21 ` [kvm-unit-tests PATCH v4 2/5] riscv: use asm-offsets to generate SBI_EXT_HSM values Clément Léger
2025-01-07 17:27   ` Andrew Jones
2025-01-07 17:33     ` Clément Léger
2024-11-25 16:21 ` [kvm-unit-tests PATCH v4 3/5] riscv: Add "-deps" handling for tests Clément Léger
2024-11-25 16:21 ` [kvm-unit-tests PATCH v4 4/5] riscv: lib: Add SBI SSE extension definitions Clément Léger
2025-01-08 13:03   ` Andrew Jones
2025-01-08 18:34     ` Atish Kumar Patra
2024-11-25 16:21 ` [kvm-unit-tests PATCH v4 5/5] riscv: sbi: Add SSE extension tests Clément Léger
2025-01-13 17:19   ` Andrew Jones
2025-01-13 17:22     ` Andrew Jones [this message]
2025-01-14 11:59   ` Andrew Jones
2025-02-13  9:27     ` Clément Léger
2025-01-06 10:11 ` [kvm-unit-tests PATCH v4 0/5] riscv: add SBI " Clément Léger
2025-01-06 13:55   ` Andrew Jones

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=20250113-5f909e9cad611aa6b69c52fc@orel \
    --to=andrew.jones@linux.dev \
    --cc=ajones@ventanamicro.com \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.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