All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: <linux-kernel@vger.kernel.org>, Jiri Kosina <trivial@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH trivial] bootconfig: Fixup one typo
Date: Sun, 10 May 2020 16:51:42 +0900	[thread overview]
Message-ID: <20200510165142.f3b37689aa1b5ee1c5a5e414@kernel.org> (raw)
In-Reply-To: <1589013235-56363-1-git-send-email-zhangshaokun@hisilicon.com>

On Sat, 9 May 2020 16:33:55 +0800
Shaokun Zhang <zhangshaokun@hisilicon.com> wrote:

> Fix up one typo: CONFIG_BOOTCONFIG -> CONFIG_BOOT_CONFIG
> 
> Cc: Jiri Kosina <trivial@kernel.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Shaokun Zhang <zhangshaokun@hisilicon.com>

Good catch! Thanks!

Acked-by: Masami Hiramatsu <mhiramat@kernel.org>

> ---
>  init/main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/init/main.c b/init/main.c
> index 1a5da2c2660c..8369ba173ad8 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -460,7 +460,7 @@ static void __init setup_boot_config(const char *cmdline)
>  
>  static int __init warn_bootconfig(char *str)
>  {
> -	pr_warn("WARNING: 'bootconfig' found on the kernel command line but CONFIG_BOOTCONFIG is not set.\n");
> +	pr_warn("WARNING: 'bootconfig' found on the kernel command line but CONFIG_BOOT_CONFIG is not set.\n");
>  	return 0;
>  }
>  early_param("bootconfig", warn_bootconfig);
> -- 
> 2.7.4
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2020-05-10  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  8:33 [PATCH trivial] bootconfig: Fixup one typo Shaokun Zhang
2020-05-10  7:51 ` Masami Hiramatsu [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=20200510165142.f3b37689aa1b5ee1c5a5e414@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=trivial@kernel.org \
    --cc=zhangshaokun@hisilicon.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.