Linux CXL
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: <alison.schofield@intel.com>, Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 0/2] Return EBUSY on inject poison limit reached
Date: Wed, 3 Jul 2024 18:00:39 -0700	[thread overview]
Message-ID: <6685f4371c47c_4fe7f294b4@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <cover.1720052137.git.alison.schofield@intel.com>

alison.schofield@ wrote:
> From: Alison Schofield <alison.schofield@intel.com>
> 
> Validation users are asking for the ability to recognize when
> their injection testing has hit the limit of the device.
> 
> Change the drivers error code for this failure to EBUSY and do
> the same in the cxl-test mock of inject poison.
> 
> 
> Alison Schofield (2):
>   cxl/memdev: Replace ENXIO with EBUSY for inject poison limit reached
>   cxl/test: Replace ENXIO with EBUSY for inject poison limit reached
> 
>  Documentation/ABI/testing/debugfs-cxl |  7 ++++---
>  drivers/cxl/cxlmem.h                  |  2 +-
>  tools/testing/cxl/test/mem.c          | 13 ++++++-------
>  3 files changed, 11 insertions(+), 11 deletions(-)

Looks good to me:

Reviewed-by: Dan Williams <dan.j.williams@intel.com>

  parent reply	other threads:[~2024-07-04  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  0:38 [PATCH 0/2] Return EBUSY on inject poison limit reached alison.schofield
2024-07-04  0:38 ` [PATCH 1/2] cxl/memdev: Replace ENXIO with EBUSY for " alison.schofield
2024-07-05  6:59   ` Xingtao Yao (Fujitsu)
2024-07-04  0:38 ` [PATCH 2/2] cxl/test: " alison.schofield
2024-07-05  6:15   ` Xingtao Yao (Fujitsu)
2024-07-07  1:48     ` Alison Schofield
2024-07-04  1:00 ` Dan Williams [this message]
2024-07-06  2:05 ` [PATCH 0/2] Return EBUSY on " Davidlohr Bueso

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=6685f4371c47c_4fe7f294b4@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.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