From: Davidlohr Bueso <dave@stgolabs.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: mst@redhat.com, jonathan.cameron@huawei.com,
qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v3 -qemu 0/2] hw/cxl: Media Operation Discovery fixlets
Date: Tue, 24 Mar 2026 12:15:34 -0700 [thread overview]
Message-ID: <20260324191534.uc3tnircy6fse7cw@offworld> (raw)
In-Reply-To: <96061f5f-cdda-4bf1-9ab4-97400fcc9344@tls.msk.ru>
On Tue, 24 Mar 2026, Michael Tokarev wrote:
>On 19.03.2026 21:42, Davidlohr Bueso wrote:
>>Hello,
>>
>>Changes from v2: indent fix in patch 1. Added reviewed+fixes tags.
>>Changes from v1: cleaned up comments in patch 2.
>>
>>While working on the driver side of this, I tripped on two qemu issues
>>around discovery semantics. I think this is the first time these code
>>paths are exercised.
>>
>>Davidlohr Bueso (2):
>> hw/cxl: Respect Media Operation max ops discovery semantics
>> hw/cxl: Exclude Discovery from Media Operation Discovery output
>
>Hi!
>
>I'm picking this series up for qemu-stable (10.2.x).
>
Yes, please do. Thanks!
prev parent reply other threads:[~2026-03-24 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:42 [PATCH v3 -qemu 0/2] hw/cxl: Media Operation Discovery fixlets Davidlohr Bueso
2026-03-19 18:42 ` [PATCH 1/2] hw/cxl: Respect Media Operation max ops discovery semantics Davidlohr Bueso
2026-03-19 18:42 ` [PATCH 2/2] hw/cxl: Exclude Discovery from Media Operation Discovery output Davidlohr Bueso
2026-03-24 13:25 ` [PATCH v3 -qemu 0/2] hw/cxl: Media Operation Discovery fixlets Michael Tokarev
2026-03-24 19:15 ` Davidlohr Bueso [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=20260324191534.uc3tnircy6fse7cw@offworld \
--to=dave@stgolabs.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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