Linux CXL
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
	ira.weiny@intel.com, vishal.l.verma@intel.com,
	alison.schofield@intel.com, Jonathan.Cameron@huawei.com,
	jgg@nvidia.com, shiju.jose@huawei.com,
	Li Ming <ming.li@zohomail.com>
Subject: Re: [PATCH v7 01/14] cxl: Enumerate feature commands
Date: Tue, 25 Feb 2025 13:09:08 -0800	[thread overview]
Message-ID: <20250225210908.d3leh62kcikm3yi5@offworld> (raw)
In-Reply-To: <20250220194438.2281088-2-dave.jiang@intel.com>

On Thu, 20 Feb 2025, Dave Jiang wrote:

>Add feature commands enumeration code in order to detect and enumerate
>the 3 feature related commands "get supported features", "get feature",
>and "set feature". The enumeration will help determine whether the driver
>can issue any of the 3 commands to the device.
>
>Reviewed-by: Dan Williams <dan.j.williams@intel.com>
>Reviewed-by: Li Ming <ming.li@zohomail.com>
>Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>Tested-by: Shiju Jose <shiju.jose@huawei.com>
>Signed-off-by: Dave Jiang <dave.jiang@intel.com>

Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>

  reply	other threads:[~2025-02-25 21:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 19:42 [PATCH v7 00/14] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-20 19:42 ` [PATCH v7 01/14] cxl: Enumerate feature commands Dave Jiang
2025-02-25 21:09   ` Davidlohr Bueso [this message]
2025-02-20 19:42 ` [PATCH v7 02/14] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-25 21:01   ` Davidlohr Bueso
2025-02-26 15:31     ` Dave Jiang
2025-02-20 19:42 ` [PATCH v7 03/14] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-20 19:42 ` [PATCH v7 04/14] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-20 19:42 ` [PATCH v7 05/14] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-20 19:42 ` [PATCH v7 06/14] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-20 19:42 ` [PATCH v7 07/14] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-20 19:42 ` [PATCH v7 08/14] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-20 19:42 ` [PATCH v7 09/14] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-20 19:42 ` [PATCH v7 10/14] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-20 19:42 ` [PATCH v7 11/14] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-20 19:42 ` [PATCH v7 12/14] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-20 19:42 ` [PATCH v7 13/14] cxl/test: Add Set " Dave Jiang
2025-02-20 19:42 ` [PATCH v7 14/14] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-25 17:54 ` [PATCH v7 00/14] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-26 16:02   ` Dave Jiang

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=20250225210908.d3leh62kcikm3yi5@offworld \
    --to=dave@stgolabs.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=jgg@nvidia.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=shiju.jose@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