From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Li Ming <ming.li@zohomail.com>
Cc: <dave@stgolabs.net>, <dave.jiang@intel.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
<shiju.jose@huawei.com>, <andriy.shevchenko@linux.intel.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 3/3] cxl/core: Using cxl_resource_contains_addr() to check address availability
Date: Fri, 11 Jul 2025 17:39:14 +0100 [thread overview]
Message-ID: <20250711173914.00004df6@huawei.com> (raw)
In-Reply-To: <20250711032357.127355-4-ming.li@zohomail.com>
On Fri, 11 Jul 2025 11:23:57 +0800
Li Ming <ming.li@zohomail.com> wrote:
> Helper function cxl_resource_contains_addr() can be used to check if a
> resource range contains an input address. Use it to replace all code
> that checks whether a resource range contains a DPA/HPA/SPA.
>
> Signed-off-by: Li Ming <ming.li@zohomail.com>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
Nice
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
next prev parent reply other threads:[~2025-07-11 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 3:23 [PATCH v6 0/3] Fix wrong dpa checking in PPR operation Li Ming
2025-07-11 3:23 ` [PATCH v6 1/3] cxl/core: Introduce a new helper cxl_resource_contains_addr() Li Ming
2025-07-11 16:20 ` Alison Schofield
2025-07-11 16:37 ` Jonathan Cameron
2025-07-11 3:23 ` [PATCH v6 2/3] cxl/edac: Fix wrong dpa checking for PPR operation Li Ming
2025-07-11 16:38 ` Jonathan Cameron
2025-07-11 3:23 ` [PATCH v6 3/3] cxl/core: Using cxl_resource_contains_addr() to check address availability Li Ming
2025-07-11 16:39 ` Jonathan Cameron [this message]
2025-07-11 16:57 ` [PATCH v6 0/3] Fix wrong dpa checking in PPR operation 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=20250711173914.00004df6@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.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=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
all inboxes | Powered by JetHome®