From: Richard Cheng <icheng@nvidia.com>
To: Praveen Rajendran <praveenrajendran2009@gmail.com>
Cc: dave@stgolabs.net, jic23@kernel.org, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
djbw@kernel.org, iweiny@kernel.org, ming.li@zohomail.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cxl: Fix spelling typo in asynchronous event string
Date: Sat, 4 Jul 2026 18:56:56 +0800 [thread overview]
Message-ID: <akjmxFrZFbmbzYex@MWDK4CY14F> (raw)
In-Reply-To: <20260703145250.3953-1-praveenrajendran2009@gmail.com>
On Fri, Jul 03, 2026 at 08:22:50PM +0800, Praveen Rajendran wrote:
> Correct a user-facing spelling mistake in the CXL memory error logging
> macro array where "occurred" was misspelled as "occured".
>
> Signed-off-by: Praveen Rajendran <praveenrajendran2009@gmail.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 ed419d0c59f2..503ae2864591 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"), \
> --
> 2.50.1
>
>
Reviewed-by: Richard Cheng <icheng@nvidia.com>
Best regards,
Richard Cheng.
next prev parent reply other threads:[~2026-07-04 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:52 [PATCH] cxl: Fix spelling typo in asynchronous event string Praveen Rajendran
2026-07-04 10:56 ` Richard Cheng [this message]
2026-07-06 18:10 ` 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=akjmxFrZFbmbzYex@MWDK4CY14F \
--to=icheng@nvidia.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@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=praveenrajendran2009@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox