From: Alison Schofield <alison.schofield@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <dave.jiang@intel.com>, <patches@lists.linux.dev>,
<linux-cxl@vger.kernel.org>,
<Smita.KoralahalliChannabasappa@amd.com>
Subject: Re: [PATCH 7/9] dax/hmem: Parent dax_hmem devices
Date: Fri, 27 Mar 2026 16:47:28 -0700 [thread overview]
Message-ID: <accXEP3yC239Noxe@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260327052821.440749-8-dan.j.williams@intel.com>
On Thu, Mar 26, 2026 at 10:28:19PM -0700, Dan Williams wrote:
> For test purposes it is useful to be able to determine which
> "hmem_platform" device is hosting a given sub-device.
>
> Register hmem devices underneath "hmem_platform".
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
next prev parent reply other threads:[~2026-03-27 23:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 5:28 [PATCH 0/9] dax/hmem: Add tests for the dax_hmem takeover capability Dan Williams
2026-03-27 5:28 ` [PATCH 1/9] cxl/region: Fix use-after-free from auto assembly failure Dan Williams
2026-03-27 16:28 ` Dave Jiang
2026-03-27 19:20 ` Alison Schofield
2026-03-27 21:54 ` Dan Williams
2026-03-27 22:37 ` Alison Schofield
2026-03-27 23:43 ` Alison Schofield
2026-03-30 20:24 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 2/9] dax/cxl: Fix HMEM dependencies Dan Williams
2026-03-27 16:29 ` Dave Jiang
2026-03-27 23:44 ` Alison Schofield
2026-03-30 21:10 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 3/9] cxl/region: Limit visibility of cxl_region_contains_resource() Dan Williams
2026-03-27 16:39 ` Dave Jiang
2026-03-27 23:45 ` Alison Schofield
2026-03-30 22:19 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 4/9] cxl/region: Constify cxl_region_resource_contains() Dan Williams
2026-03-27 16:40 ` Dave Jiang
2026-03-27 23:45 ` Alison Schofield
2026-03-30 22:22 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 5/9] dax/hmem: Reduce visibility of dax_cxl coordination symbols Dan Williams
2026-03-27 16:46 ` Dave Jiang
2026-03-27 23:46 ` Alison Schofield
2026-03-30 22:26 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 6/9] dax/hmem: Fix singleton confusion between dax_hmem_work and hmem devices Dan Williams
2026-03-27 17:06 ` Dave Jiang
2026-03-27 23:46 ` Alison Schofield
2026-03-31 17:32 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 7/9] dax/hmem: Parent dax_hmem devices Dan Williams
2026-03-27 17:07 ` Dave Jiang
2026-03-27 23:47 ` Alison Schofield [this message]
2026-03-31 17:42 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 8/9] tools/testing/cxl: Simulate auto-assembly failure Dan Williams
2026-03-27 17:08 ` Dave Jiang
2026-03-27 23:48 ` Alison Schofield
2026-03-31 17:43 ` Ira Weiny
2026-03-27 5:28 ` [PATCH 9/9] tools/testing/cxl: Test dax_hmem takeover of CXL regions Dan Williams
2026-03-27 17:10 ` Dave Jiang
2026-03-27 23:58 ` Alison Schofield
2026-03-28 3:20 ` Dan Williams
2026-03-31 17:57 ` Ira Weiny
2026-03-31 18:13 ` Alison Schofield
2026-03-27 23:42 ` [PATCH 0/9] dax/hmem: Add tests for the dax_hmem takeover capability Alison Schofield
2026-03-30 21:12 ` Koralahalli Channabasappa, Smita
2026-03-30 21:17 ` Dave Jiang
2026-03-31 21:57 ` 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=accXEP3yC239Noxe@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=patches@lists.linux.dev \
/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