From: Jeuk Kim <jeuk20.kim@gmail.com>
To: yc01.jeong@samsung.com, Jeuk Kim <jeuk20.kim@samsung.com>
Cc: "thuth@redhat.com" <thuth@redhat.com>,
"lvivier@redhat.com" <lvivier@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jeongyuchan0629@gmail.com" <jeongyuchan0629@gmail.com>
Subject: Re: [PATCH v2 0/4] hw/ufs: ufs device testing function added and modified
Date: Mon, 26 Aug 2024 09:06:29 +0900 [thread overview]
Message-ID: <3b89ebdf-32dd-4cb9-9197-2b4137e4eb0d@gmail.com> (raw)
In-Reply-To: <20240822080846epcms1p122450de3fc0c0f8aa46db1ea00392c71@epcms1p1>
Thank you for your contribution.
Reviewed-by: Jeuk Kim <jeuk20.kim@samsung.com>
On 8/22/2024 5:08 PM, Yoochan Jeong wrote:
> Previously, it was only able to test virtual UFS devices if they properly
> read and write storage data. In this patch, three test functions are added
> to test if virtual UFS devices properly read and write its metadata.
> Each functions test reading and writing flags, attributes and descriptors.
> Related minor bugs and errors are also fixed.
>
> Yoochan Jeong (4):
> hw/ufs: minor bug fixes related to ufs-test
> hw/ufs: ufs flag read/write test implemented
> hw/ufs: ufs attribute read/write test implemented
> hw/ufs: ufs descriptor read test implemented
>
> hw/ufs/ufs.c | 19 +-
> include/block/ufs.h | 6 +
> tests/qtest/ufs-test.c | 384 ++++++++++++++++++++++++++++++++++++++++-
> 3 files changed, 400 insertions(+), 9 deletions(-)
>
prev parent reply other threads:[~2024-08-26 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240822080846epcms1p122450de3fc0c0f8aa46db1ea00392c71@epcms1p1>
2024-08-22 8:08 ` [PATCH v2 0/4] hw/ufs: ufs device testing function added and modified Yoochan Jeong
[not found] ` <CGME20240822080846epcms1p122450de3fc0c0f8aa46db1ea00392c71@epcms1p3>
2024-08-22 8:09 ` [PATCH v2 1/4] hw/ufs: minor bug fixes related to ufs-test Yoochan Jeong
[not found] ` <CGME20240822080846epcms1p122450de3fc0c0f8aa46db1ea00392c71@epcms1p8>
2024-08-22 8:11 ` [PATCH v2 3/4] hw/ufs: ufs attribute read/write test implemented Yoochan Jeong
[not found] ` <CGME20240822080846epcms1p122450de3fc0c0f8aa46db1ea00392c71@epcms1p4>
2024-08-22 8:10 ` [PATCH v2 2/4] hw/ufs: ufs flag " Yoochan Jeong
2024-08-22 8:12 ` [PATCH v2 4/4] hw/ufs: ufs descriptor read " Yoochan Jeong
2024-08-26 0:06 ` Jeuk Kim [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=3b89ebdf-32dd-4cb9-9197-2b4137e4eb0d@gmail.com \
--to=jeuk20.kim@gmail.com \
--cc=jeongyuchan0629@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yc01.jeong@samsung.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;
as well as URLs for NNTP newsgroup(s).