Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
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>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/4] Documentation/arch: fix typo "initalised" in comment
Date: Mon,  7 Sep 2026 10:09:30 +0530	[thread overview]
Message-ID: <20260907043933.33452-1-hemanth.selam@gmail.com> (raw)
In-Reply-To: <b7b77956-591f-4282-aaad-04c9f7899413@infradead.org>

Thanks for the pointer, and you are right to raise it - I checked and this
patch does fall foul of that rule.

The word in Documentation/arch/arm64/booting.rst is "zero-initalised", and
I changed it to "zero-initialized", which quietly moves the file from
British to American spelling.  The minimal fix is "zero-initialised".

I followed checkpatch here, and checkpatch is following the dictionary:

  scripts/spelling.txt:875:initalised||initialized
  scripts/spelling.txt:874:initalise||initialize

Those are the only two entries in the file that map a British form to an
American one, and by the rule you quoted they should read

  initalise||initialise
  initalised||initialised

so that the misspelling is corrected without changing the variety of
English in the file.  arch/arm64 currently has 58 uses of "initialised"
against 132 of "initialized", so both spellings are clearly in use there.

I will send a v2 that uses "zero-initialised".  Would a separate patch
fixing those two spelling.txt entries be welcome, or is that better left
alone?


  reply	other threads:[~2026-09-07  4:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260904105114.29474-1-hemanth.selam@gmail.com>
2026-09-04 10:51 ` [PATCH 1/4] Documentation/arch: fix typo "initalised" in comment Hemanth Selam
2026-09-04 22:01   ` Randy Dunlap
2026-09-07  4:39     ` Hemanth Selam [this message]
2026-09-07  5:23       ` Randy Dunlap
2026-09-04 10:51 ` [PATCH 2/4] arm64: fix typos in comments Hemanth Selam
2026-09-04 10:51 ` [PATCH 3/4] selftests: arm64: fix typo "hander" in comment Hemanth Selam
2026-09-04 10:51 ` [PATCH 4/4] arm64: include: fix repeated word 'to' " Hemanth Selam

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=20260907043933.33452-1-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --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