From: Jeuk Kim <jeuk20.kim@gmail.com>
To: daejun7.park@samsung.com, Jeuk Kim <jeuk20.kim@samsung.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: JinHwan Park <jh.i.park@samsung.com>,
Seokhwan Kim <sukka.kim@samsung.com>,
Yonggil Song <yonggil.song@samsung.com>
Subject: Re: [PATCH 1/3] hw/ufs: Support for Zoned UFS
Date: Tue, 12 Dec 2023 13:38:47 +0900 [thread overview]
Message-ID: <9c2dc260-8c3a-486f-a70f-b7ee238fe097@gmail.com> (raw)
In-Reply-To: <20231208061330epcms2p2f742a2d517b6836eca695a9b59bd109c@epcms2p2>
On 12/8/2023 3:13 PM, Daejun Park wrote:
> This patch enables zoned ufs support.
>
> By setting the LU parameter, each LU can be a host-managed zoned device.
> This patch manages the zone condition and write pointer of each zone for
> a zoned LU. It supports the report zones and reset write pointer commands
> for Zoned LUs.
>
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
Reviewed-by: Jeuk Kim <jeuk20.kim@samsung.com>
next prev parent reply other threads:[~2023-12-12 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231208060902epcms2p3810b29fefbddaf16a7f3f2758cf218ba@epcms2p3>
2023-12-08 6:09 ` [PATCH 0/3] Support for Zoned UFS Daejun Park
[not found] ` <CGME20231208060902epcms2p3810b29fefbddaf16a7f3f2758cf218ba@epcms2p2>
2023-12-08 6:13 ` [PATCH 1/3] hw/ufs: " Daejun Park
2023-12-12 4:38 ` Jeuk Kim [this message]
[not found] ` <CGME20231208060902epcms2p3810b29fefbddaf16a7f3f2758cf218ba@epcms2p4>
2023-12-08 6:20 ` [PATCH 2/3] hw/scsi: add mode sense support for zbc device Daejun Park
[not found] ` <CGME20231208060902epcms2p3810b29fefbddaf16a7f3f2758cf218ba@epcms2p7>
2023-12-08 6:22 ` [PATCH 3/3] tests/qtest: Add tests for Zoned UFS Daejun Park
2023-12-12 4:39 ` Jeuk Kim
2023-12-12 4:40 ` [PATCH 0/3] Support " Jeuk Kim
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=9c2dc260-8c3a-486f-a70f-b7ee238fe097@gmail.com \
--to=jeuk20.kim@gmail.com \
--cc=daejun7.park@samsung.com \
--cc=fam@euphon.net \
--cc=jeuk20.kim@samsung.com \
--cc=jh.i.park@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sukka.kim@samsung.com \
--cc=yonggil.song@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).