From: Ira Weiny <ira.weiny@intel.com>
To: Gregory Price <gourry@gourry.net>, <linux-cxl@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@meta.com>,
<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
<dave.jiang@intel.com>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<dan.j.williams@intel.com>
Subject: Re: [PATCH v5 2/3] cxl/core/region: move dax region device logic into region_dax.c
Date: Fri, 27 Mar 2026 11:57:22 -0500 [thread overview]
Message-ID: <69c6b6f2d9089_1771f410066@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20260327020203.876122-3-gourry@gourry.net>
Gregory Price wrote:
> core/region.c is overloaded with per-region control logic (pmem, dax,
> sysram, etc). Move the CXL DAX region device infrastructure from
> region.c into a new region_dax.c file.
>
> This will also allow us to add additional dax-driver integration paths
> that don't further dirty the core region.c logic.
>
> No functional changes.
>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Co-developed-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> ---
[snip]
next prev parent reply other threads:[~2026-03-27 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 2:02 [PATCH v5 0/3] pull region-specific logic into new files Gregory Price
2026-03-27 2:02 ` [PATCH v5 1/3] cxl/core/region: move pmem region driver logic into region_pmem.c Gregory Price
2026-03-27 16:56 ` Ira Weiny
2026-03-27 2:02 ` [PATCH v5 2/3] cxl/core/region: move dax region device logic into region_dax.c Gregory Price
2026-03-27 16:57 ` Ira Weiny [this message]
2026-04-11 0:02 ` Anisa Su
2026-04-11 0:26 ` Dave Jiang
2026-04-11 5:09 ` Gregory Price
2026-04-11 17:39 ` Dan Williams
2026-04-13 17:00 ` Anisa Su
2026-03-27 2:02 ` [PATCH v5 3/3] cxl/core: use cleanup.h for devm_cxl_add_dax_region Gregory Price
2026-03-27 17:05 ` Ira Weiny
2026-03-27 18:57 ` [PATCH v5 0/3] pull region-specific logic into new files 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=69c6b6f2d9089_1771f410066@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.