Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: arm64: Fix typo "initalised" in booting.rst
Date: Mon, 7 Sep 2026 18:27:43 +0800	[thread overview]
Message-ID: <ap6Rn5We1wDJ3KkK@wyuan.org> (raw)
In-Reply-To: <20260907091248.31415-1-hemanth.selam@gmail.com>

On Mon, Sep 07, 2026 at 02:42:48PM +0530, Hemanth Selam wrote:
> Correct the misspelling "initalised" in the arm64 booting document.
> 
> v1 changed it to "initialized", which quietly moved the file from
> British to American spelling.  Randy Dunlap pointed out that
> doc-guide/checkpatch.rst asks that both spellings be left alone, so

doc-guide/contributing.rst ?

There's no checkpatch.rst in doc-guide, I guess.

> this uses "initialised" and only fixes the missing "i".

And, future readers may not know what was in v1. Or rather, I don't
think mentioning v1 here adds much.

But I think a brief summary of your discussion with Randy in the
previous round might be useful.?

> checkpatch.pl suggested "initialized" because scripts/spelling.txt maps
> these two entries to the American form; that is addressed separately.

> Only the documentation text changes.

Nit: You seem to prefer spelling this out, but the diff is fairly
     straightforward. Do we really need to mention it explicitly?

> Assisted-by: Cursor:claude-opus-5

Of course, I don't know whether this commit message was written by it.
;-)



      reply	other threads:[~2026-09-07 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  9:12 [PATCH v2] docs: arm64: Fix typo "initalised" in booting.rst Hemanth Selam
2026-09-07 10:27 ` Weijie Yuan [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=ap6Rn5We1wDJ3KkK@wyuan.org \
    --to=wy@wyuan.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=will@kernel.org \
    /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