All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crash: Fix spelling mistake "crahskernel" -> "crashkernel"
Date: Fri, 18 Apr 2025 21:07:58 +0800	[thread overview]
Message-ID: <aAJOrrRMe7ohIaqj@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250418120331.535086-1-colin.i.king@gmail.com>

On 04/18/25 at 01:03pm, Colin Ian King wrote:
> There is a spelling mistake in a pr_warn message. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  kernel/crash_reserve.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index aff7c0fdbefa..acb6bf42e30d 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -131,7 +131,7 @@ static int __init parse_crashkernel_mem(char *cmdline,
>  			cur++;
>  			*crash_base = memparse(cur, &tmp);
>  			if (cur == tmp) {
> -				pr_warn("crahskernel: Memory value expected after '@'\n");
> +				pr_warn("crashkernel: Memory value expected after '@'\n");
>  				return -EINVAL;

Acked-by: Baoquan He <bhe@redhat.com>

>  			}
>  		}
> -- 
> 2.49.0
> 



  reply	other threads:[~2025-04-18 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 12:03 [PATCH] crash: Fix spelling mistake "crahskernel" -> "crashkernel" Colin Ian King
2025-04-18 13:07 ` Baoquan He [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-19  8:52 [PATCH] crash: Fix spelling mistake: " Colin Ian King
2024-04-19  8:52 ` Colin Ian King
2024-04-23 10:09 ` Simon Horman
2024-04-23 10:09   ` Simon Horman

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=aAJOrrRMe7ohIaqj@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.