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>
---
 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.

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.