mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
	Li Ming <ming.li@zohomail.com>, <linux-kernel@vger.kernel.org>,
	<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] tools/testing: fix typo "occuring" in comment
Date: Fri, 4 Sep 2026 09:18:56 -0700	[thread overview]
Message-ID: <aprvcDMx4X09jnzI@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260904104013.11549-1-hemanth.selam@gmail.com>

On Fri, Sep 04, 2026 at 04:10:12PM +0530, Hemanth Selam wrote:
> Correct "occuring" to "occurring", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt.  Only touches comments, no
> code changes.

Hi Hemanth,

Spelling corrections to code comments, which are not user facing,
are too trivial to be worth the churn. Sometimes folks make a spelling
correction like this while they are doing 'something else' in that
code.

For for CXL subsystem, the better place to point your tool is at the
mailing list where you are welcome to review patches and reply with
spelling issues in any patch commit messaging, user facing messaging,
and code comments - before the patch merges.

-- Alison


> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
>  tools/testing/cxl/test/mem.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> index 7b756000a1a6..3d8a6d2b69d7 100644
> --- a/tools/testing/cxl/test/mem.c
> +++ b/tools/testing/cxl/test/mem.c
> @@ -246,7 +246,7 @@ static void mes_add_event(struct mock_event_store *mes,
>  }
>  
>  /*
> - * Vary the number of events returned to simulate events occuring while the
> + * Vary the number of events returned to simulate events occurring while the
>   * logs are being read.
>   */
>  static atomic_t event_counter = ATOMIC_INIT(0);
> -- 
> 2.48.1
> 

      reply	other threads:[~2026-09-04 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 10:40 Hemanth Selam
2026-09-04 16:18 ` 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=aprvcDMx4X09jnzI@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=hemanth.selam@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®