public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dave@stgolabs.net>,
	<jonathan.cameron@huawei.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>
Subject: Re: [PATCH 0/2] cxl: Fix nvdimm_bus race for nvdimm_bridge
Date: Fri, 20 Feb 2026 17:03:39 -0800	[thread overview]
Message-ID: <aZkEayARHFqMe63d@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260205001633.1813643-1-dave.jiang@intel.com>

On Wed, Feb 04, 2026 at 05:16:31PM -0700, Dave Jiang wrote:
> A small series to address a race for nvdimm_bus object when using the
> nvdimm_bridge object.
> 
Hi Dave,

Sorry for the delay tagging. I was hoping to find a crisp
reproducer to add to the commit log, but nothing nice enough
for a unit test, yet!

For the series:
Tested-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Alison Schofield <alison.schofield@intel.com?


> 
> Dave Jiang (2):
>   cxl/test: Removal of nvdimm_bus_register() wrapper in cxl_test
>   cxl: Fix race of nvdimm_bus for the nvdimm_bridge object
> 
>  drivers/cxl/core/pmem.c       | 236 +++++++++++++++++++++++++++++++---
>  drivers/cxl/pmem.c            | 199 +---------------------------
>  include/linux/libnvdimm.h     |   2 +-
>  tools/testing/cxl/Kbuild      |   1 -
>  tools/testing/cxl/test/mock.c |  15 ---
>  5 files changed, 221 insertions(+), 232 deletions(-)
> 
> 
> base-commit: 18f7fcd5e69a04df57b563360b88be72471d6b62
> -- 
> 2.52.0
> 

      parent reply	other threads:[~2026-02-21  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  0:16 [PATCH 0/2] cxl: Fix nvdimm_bus race for nvdimm_bridge Dave Jiang
2026-02-05  0:16 ` [PATCH 1/2] cxl/test: Removal of nvdimm_bus_register() wrapper in cxl_test Dave Jiang
2026-02-09 19:30   ` Ira Weiny
2026-02-05  0:16 ` [PATCH 2/2] cxl: Fix race of nvdimm_bus for the nvdimm_bridge object Dave Jiang
2026-02-05  6:44   ` kernel test robot
2026-02-05 17:47   ` kernel test robot
2026-02-05 21:28 ` [PATCH 0/2] cxl: Fix nvdimm_bus race for nvdimm_bridge Dave Jiang
2026-02-21  1:03 ` Alison Schofield [this message]

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=aZkEayARHFqMe63d@aschofie-mobl2.lan \
    --to=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=jonathan.cameron@huawei.com \
    --cc=linux-cxl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox