kvm-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: kvm-riscv@lists.infradead.org
Cc: cleger@rivosinc.com, atishp@rivosinc.com
Subject: Re: [kvm-unit-tests PATCH v2 0/3] riscv: sbi: Provide sbiret_report/check
Date: Tue, 4 Mar 2025 10:32:21 +0100	[thread overview]
Message-ID: <20250304-02695193b45ff3d30c19b561@orel> (raw)
In-Reply-To: <20250218185401.41250-5-andrew.jones@linux.dev>

On Tue, Feb 18, 2025 at 07:54:01PM +0100, Andrew Jones wrote:
> It's commom for SBI tests to expect a particular error return (or no
> error, which case it expects the returned error to be SBI_SUCCESS).
> When we don't get the expected error it'd be nice to output what we
> did get. gen_report() in the SBI tests were doing that for the BASE
> tests, improve it and export it to be used by all SBI tests.
> 
> v2:
>  - Output expected error string with sbiret_report_error() [Clément]
>  - Picked up Clément's tags except for patch3 since it changed a
>    decent amount.
> 
> Andrew Jones (3):
>   riscv: sbi: Improve gen_report
>   riscv: sbi: Export sbiret_report/check
>   riscv: sbi: Add sbiret_report_error
> 
>  riscv/sbi-tests.h | 36 ++++++++++++++++++++++++++++++++++++
>  riscv/sbi.c       | 30 ++++++++----------------------
>  2 files changed, 44 insertions(+), 22 deletions(-)
> 
> -- 
> 2.48.1
>

Merged.

Thanks,
drew

-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

      parent reply	other threads:[~2025-03-04  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 18:54 [kvm-unit-tests PATCH v2 0/3] riscv: sbi: Provide sbiret_report/check Andrew Jones
2025-02-18 18:54 ` [kvm-unit-tests PATCH v2 1/3] riscv: sbi: Improve gen_report Andrew Jones
2025-02-18 18:54 ` [kvm-unit-tests PATCH v2 2/3] riscv: sbi: Export sbiret_report/check Andrew Jones
2025-02-18 18:54 ` [kvm-unit-tests PATCH v2 3/3] riscv: sbi: Add sbiret_report_error Andrew Jones
2025-02-25 10:10   ` Clément Léger
2025-03-04  9:32 ` Andrew Jones [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=20250304-02695193b45ff3d30c19b561@orel \
    --to=andrew.jones@linux.dev \
    --cc=atishp@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=kvm-riscv@lists.infradead.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).