From: Svetly Todorov <svetly.todorov@memverge.com>
To: "nifan.cxl@gmail.com" <nifan.cxl@gmail.com>
Cc: "Jorgen.Hansen@wdc.com" <Jorgen.Hansen@wdc.com>,
"a.manzanares@samsung.com" <a.manzanares@samsung.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"fan.ni@samsung.com" <fan.ni@samsung.com>,
Gregory Price <gregory.price@memverge.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"jim.harris@samsung.com" <jim.harris@samsung.com>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nmtadam.samsung@gmail.com" <nmtadam.samsung@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"wj28.lee@gmail.com" <wj28.lee@gmail.com>
Subject: Re: [PATCH v7 00/12] Enabling DCD emulation support in Qemu
Date: Wed, 24 Apr 2024 20:16:15 +0000 [thread overview]
Message-ID: <7489170B-E7CC-49BB-91D9-DD6497F99E23@memverge.com> (raw)
I tested the v7 DC add/release as part of the MHSLD RFC work I did
with Gregory. Those commands worked as expected. Feel free to tack on:
Tested-by: Svetly Todorov <svetly.todorov@memverge.com <mailto:svetly.todorov@memverge.com>>
next reply other threads:[~2024-04-24 20:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 20:16 Svetly Todorov [this message]
2024-04-24 20:28 ` [PATCH v7 00/12] Enabling DCD emulation support in Qemu Svetly Todorov
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 23:10 nifan.cxl
2024-04-19 18:24 ` Gregory Price
2024-04-19 18:43 ` fan
2024-04-20 20:35 ` Gregory Price
2024-04-22 12:04 ` Jonathan Cameron
2024-04-22 14:23 ` Jonathan Cameron
2024-04-22 15:07 ` Jonathan Cameron
2024-04-22 15:42 ` Gregory Price
2024-05-16 17:05 ` fan
2024-05-17 12:18 ` Jonathan Cameron
2024-05-17 16:03 ` fan
2024-05-28 18:10 ` Gregory Price
2024-05-14 2:16 ` Zhijian Li (Fujitsu)
2024-05-16 17:12 ` fan
2024-05-17 2:20 ` Zhijian Li (Fujitsu)
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=7489170B-E7CC-49BB-91D9-DD6497F99E23@memverge.com \
--to=svetly.todorov@memverge.com \
--cc=Jorgen.Hansen@wdc.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gregory.price@memverge.com \
--cc=ira.weiny@intel.com \
--cc=jim.harris@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan.cxl@gmail.com \
--cc=nmtadam.samsung@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wj28.lee@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).