From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: <shiju.jose@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
<armbru@redhat.com>, <dave@stgolabs.net>, <linuxarm@huawei.com>
Subject: Re: [PATCH v5 1/7] hw/cxl/events: Update for rev3.2 common event record format
Date: Fri, 8 Aug 2025 14:29:07 +0100 [thread overview]
Message-ID: <20250808142907.000022f4@huawei.com> (raw)
In-Reply-To: <20250807154346.2209-2-shiju.jose@huawei.com>
On Thu, 7 Aug 2025 16:43:40 +0100
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> CXL spec 3.2 section 8.2.9.2.1 Table 8-55, Common Event Record
> format has updated with optional Maintenance Operation Subclass,
> LD ID and ID of the device head information.
>
> Add updates for the above optional parameters in the related
> CXL events reporting and in the QMP commands to inject CXL events.
>
> In qapi/cxl.json added fields of Common Event Record to a common
> structure CXLCommonEventBase.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Hi Shiju,
Sign off chain doesn't make sense. Drop my SoB. I guess this is because
it went through my tree at some stage and hence was tagged by
me. Given it's your patch, you should drop that from new versions.
Jonathan
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
next prev parent reply other threads:[~2025-08-08 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 15:43 [PATCH v5 0/7] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 1/7] hw/cxl/events: Update for rev3.2 common event record format shiju.jose--- via
2025-08-08 10:37 ` Markus Armbruster
2025-08-08 14:04 ` Shiju Jose via
2025-08-08 13:29 ` Jonathan Cameron via [this message]
2025-08-08 14:04 ` Shiju Jose via
2025-08-07 15:43 ` [PATCH v5 2/7] hw/cxl/events: Updates for rev3.2 general media event record shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 3/7] hw/cxl/events: Updates for rev3.2 DRAM " shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 4/7] hw/cxl/events: Updates for rev3.2 memory module " shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 5/7] hw/cxl/cxl-mailbox-utils: Move declaration of scrub and ECS feature attributes in cmd_features_set_feature() shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 6/7] hw/cxl: Add support for Maintenance command and Post Package Repair (PPR) shiju.jose--- via
2025-08-07 15:43 ` [PATCH v5 7/7] hw/cxl: Add emulation for memory sparing control feature shiju.jose--- via
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=20250808142907.000022f4@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=armbru@redhat.com \
--cc=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=shiju.jose@huawei.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).