From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <shiju.jose@huawei.com>
Cc: <dave.jiang@intel.com>, <dan.j.williams@intel.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dave@stgolabs.net>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <tanxiaofei@huawei.com>,
<prime.zeng@hisilicon.com>
Subject: Re: [RFC PATCH 1/4] cxl/events: Updates for CXL Common Event Record Format
Date: Thu, 17 Oct 2024 13:19:49 +0100 [thread overview]
Message-ID: <20241017131949.000047f6@Huawei.com> (raw)
In-Reply-To: <20241016163349.1210-2-shiju.jose@huawei.com>
On Wed, 16 Oct 2024 17:33:46 +0100
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> CXL spec 3.1 section 8.2.9.2.1 Table 8-42, Common Event Record format has
> updated with Maintenance Operation Subclass information.
>
> Add updates for the above spec change in the CXL events record and CXL
> common trace event implementations.
>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2024-10-17 12:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 16:33 [RFC PATCH 0/4] Updates for CXL Event Records shiju.jose
2024-10-16 16:33 ` [RFC PATCH 1/4] cxl/events: Updates for CXL Common Event Record Format shiju.jose
2024-10-17 12:19 ` Jonathan Cameron [this message]
2024-10-16 16:33 ` [RFC PATCH 2/4] cxl/events: Updates for CXL General Media Event Record shiju.jose
2024-10-17 12:25 ` Jonathan Cameron
2024-10-17 14:42 ` Shiju Jose
2024-10-16 16:33 ` [RFC PATCH 3/4] cxl/events: Updates for CXL DRAM " shiju.jose
2024-10-17 12:38 ` Jonathan Cameron
2024-10-16 16:33 ` [RFC PATCH 4/4] cxl/events: Updates for CXL Memory Module " shiju.jose
2024-10-17 12:44 ` Jonathan Cameron
2024-10-17 14:43 ` Shiju Jose
2024-10-16 21:01 ` [RFC PATCH 0/4] Updates for CXL Event Records Alison Schofield
2024-10-17 9:39 ` Shiju Jose
2024-10-17 12:16 ` Jonathan Cameron
2024-10-18 11:04 ` Jonathan Cameron
2024-10-18 12:09 ` Shiju Jose
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=20241017131949.000047f6@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
--cc=vishal.l.verma@intel.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