mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Hemanth Selam <hemanth.selam@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k: fix typo "eanble" in comment
Date: Mon, 7 Sep 2026 15:13:29 +1000	[thread overview]
Message-ID: <347c0282-4cc0-4583-8aa3-7c7fbd59b14d@linux-m68k.org> (raw)
In-Reply-To: <20260904112245.37109-1-hemanth.selam@gmail.com>

Hi Hemanth,

On 4/9/26 21:22, Hemanth Selam wrote:
> Correct "eanble" to "Enable", reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>

This is related to ColdFire support, so I will apply to for-next branch of
m68knommu git tree.

Thanks
Greg


> ---
>  arch/m68k/include/asm/m53xxacr.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/m68k/include/asm/m53xxacr.h b/arch/m68k/include/asm/m53xxacr.h
> index 692f90e7fecc..a29ad33aaf05 100644
> --- a/arch/m68k/include/asm/m53xxacr.h
> +++ b/arch/m68k/include/asm/m53xxacr.h
> @@ -32,7 +32,7 @@
>  #define CACR_DCM_PRE	0x00000200	/* Cache inhibited, precise */
>  #define CACR_DCM_IMPRE	0x00000300	/* Cache inhibited, imprecise */
>  #define CACR_WPROTECT	0x00000020	/* Write protect*/
> -#define CACR_EUSP	0x00000010	/* Eanble separate user a7 */
> +#define CACR_EUSP	0x00000010	/* Enable separate user a7 */
>  
>  /*
>   * Define the Access Control register flags.


      reply	other threads:[~2026-09-07  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 11:22 Hemanth Selam
2026-09-07  5:13 ` Greg Ungerer [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=347c0282-4cc0-4583-8aa3-7c7fbd59b14d@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®