public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: fan <nifan.cxl@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cxl/trace: Fix uncorrectable macro spelling
Date: Thu, 22 Feb 2024 10:52:28 -0800	[thread overview]
Message-ID: <ZdeX7KRZmm35qwCY@debian> (raw)
In-Reply-To: <20240221-fix-correctable-macro-v1-1-6e6ab8b8aa39@intel.com>

On Wed, Feb 21, 2024 at 08:52:28PM -0800, Ira Weiny wrote:
> Uncorrectable is spelled with two r's.
> 
> Fix the macro spelling.
> 
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> ---

Reviewed-by: Fan Ni <fan.ni@samsung.com>

>  drivers/cxl/core/trace.h     | 4 ++--
>  tools/testing/cxl/test/mem.c | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/cxl/core/trace.h b/drivers/cxl/core/trace.h
> index bdf117a33744..577a01954f71 100644
> --- a/drivers/cxl/core/trace.h
> +++ b/drivers/cxl/core/trace.h
> @@ -267,11 +267,11 @@ TRACE_EVENT(cxl_generic_event,
>   * General Media Event Record - GMER
>   * CXL rev 3.0 Section 8.2.9.2.1.1; Table 8-43
>   */
> -#define CXL_GMER_EVT_DESC_UNCORECTABLE_EVENT		BIT(0)
> +#define CXL_GMER_EVT_DESC_UNCORRECTABLE_EVENT		BIT(0)
>  #define CXL_GMER_EVT_DESC_THRESHOLD_EVENT		BIT(1)
>  #define CXL_GMER_EVT_DESC_POISON_LIST_OVERFLOW		BIT(2)
>  #define show_event_desc_flags(flags)	__print_flags(flags, "|",		   \
> -	{ CXL_GMER_EVT_DESC_UNCORECTABLE_EVENT,		"UNCORRECTABLE_EVENT"	}, \
> +	{ CXL_GMER_EVT_DESC_UNCORRECTABLE_EVENT,	"UNCORRECTABLE_EVENT"	}, \
>  	{ CXL_GMER_EVT_DESC_THRESHOLD_EVENT,		"THRESHOLD_EVENT"	}, \
>  	{ CXL_GMER_EVT_DESC_POISON_LIST_OVERFLOW,	"POISON_LIST_OVERFLOW"	}  \
>  )
> diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> index 35ee41e435ab..c0c1e6b4db75 100644
> --- a/tools/testing/cxl/test/mem.c
> +++ b/tools/testing/cxl/test/mem.c
> @@ -380,7 +380,7 @@ struct cxl_test_gen_media gen_media = {
>  			.related_handle = cpu_to_le16(0),
>  		},
>  		.phys_addr = cpu_to_le64(0x2000),
> -		.descriptor = CXL_GMER_EVT_DESC_UNCORECTABLE_EVENT,
> +		.descriptor = CXL_GMER_EVT_DESC_UNCORRECTABLE_EVENT,
>  		.type = CXL_GMER_MEM_EVT_TYPE_DATA_PATH_ERROR,
>  		.transaction_type = CXL_GMER_TRANS_HOST_WRITE,
>  		/* .validity_flags = <set below> */
> 
> ---
> base-commit: a2cd3520e6085b0f9145d9c5e3d1bfa9cce4c3be
> change-id: 20240102-fix-correctable-macro-2847ce932c9c
> 
> Best regards,
> -- 
> Ira Weiny <ira.weiny@intel.com>
> 

      parent reply	other threads:[~2024-02-22 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  4:52 [PATCH] cxl/trace: Fix uncorrectable macro spelling Ira Weiny
2024-02-22 18:28 ` Dave Jiang
2024-02-22 18:52 ` fan [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=ZdeX7KRZmm35qwCY@debian \
    --to=nifan.cxl@gmail.com \
    --cc=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=linux-kernel@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