From: Dave Jiang <dave.jiang@intel.com>
To: Yousef Alhouseen <alhouseenyousef@gmail.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>
Cc: Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Li Ming <ming.li@zohomail.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cxl: fix mailbox return code description typo
Date: Wed, 24 Jun 2026 11:17:29 -0700 [thread overview]
Message-ID: <fb9ecf71-518c-4aca-9438-b3394abe62b3@intel.com> (raw)
In-Reply-To: <20260624122835.5656-1-alhouseenyousef@gmail.com>
On 6/24/26 5:28 AM, Yousef Alhouseen wrote:
> Fix a typo in the CXL mailbox command return code description for the
> interrupted-command case.
>
> Signed-off-by: Yousef Alhouseen <alhouseenyousef@gmail.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/cxlmem.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index ed419d0c5..503ae2864 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -183,7 +183,7 @@ static inline struct cxl_ep *cxl_ep_load(struct cxl_port *port,
> C(MBUNSUPPORTED, -ENXIO, "unsupported on the mailbox it was issued on"),\
> C(PAYLOADLEN, -ENXIO, "invalid payload length"), \
> C(LOG, -ENXIO, "invalid or unsupported log page"), \
> - C(INTERRUPTED, -ENXIO, "asynchronous event occured"), \
> + C(INTERRUPTED, -ENXIO, "asynchronous event occurred"), \
> C(FEATUREVERSION, -ENXIO, "unsupported feature version"), \
> C(FEATURESELVALUE, -ENXIO, "unsupported feature selection value"), \
> C(FEATURETRANSFERIP, -ENXIO, "feature transfer in progress"), \
prev parent reply other threads:[~2026-06-24 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 12:28 [PATCH] cxl: fix mailbox return code description typo Yousef Alhouseen
2026-06-24 13:42 ` Richard Cheng
2026-06-24 18:17 ` Dave Jiang [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=fb9ecf71-518c-4aca-9438-b3394abe62b3@intel.com \
--to=dave.jiang@intel.com \
--cc=alhouseenyousef@gmail.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.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 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.