From: Greg Ungerer <gerg@linux-m68k.org>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] m68k: coldfire: fix typos in reset.c comment
Date: Mon, 7 Sep 2026 15:08:44 +1000 [thread overview]
Message-ID: <a0844255-193a-41fe-9f58-40c1508ea72e@linux-m68k.org> (raw)
In-Reply-To: <20260907044545.6187-1-hemanth.selam@gmail.com>
Hi Hemanth,
On 7/9/26 14:45, Hemanth Selam wrote:
> Correct "reseting" to "resetting" and "ColdFure" to "ColdFire".
>
> v1 fixed only "reseting", which checkpatch had flagged, and left
> "ColdFure" two words earlier untouched. Josh Juran spotted it.
>
> Only touches a comment, no code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
Thanks for updating with the suggested fix to "ColdFire".
Applied to for-next branch of m68knommu git tree.
Regards
Greg
> ---
> arch/m68k/coldfire/reset.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/m68k/coldfire/reset.c b/arch/m68k/coldfire/reset.c
> index 6e5f8ab39f32..079c92593eff 100644
> --- a/arch/m68k/coldfire/reset.c
> +++ b/arch/m68k/coldfire/reset.c
> @@ -16,7 +16,7 @@
> #include <asm/mcfsim.h>
>
> /*
> - * There are 2 common methods amongst the ColdFure parts for reseting
> + * There are 2 common methods amongst the ColdFire parts for resetting
> * the CPU. But there are couple of exceptions, the 5272 and the 547x
> * have something completely special to them, and we let their specific
> * subarch code handle them.
prev parent reply other threads:[~2026-09-07 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 4:45 Hemanth Selam
2026-09-07 5:08 ` 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=a0844255-193a-41fe-9f58-40c1508ea72e@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®