public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kushagra Verma <kushagra765@outlook.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fixed a typo in bootconfig.rst
Date: Sat, 03 Dec 2022 03:49:21 -0700	[thread overview]
Message-ID: <87tu2coj7y.fsf@meer.lwn.net> (raw)
In-Reply-To: <HK0PR01MB2801DA243B726141A97FE92EF8179@HK0PR01MB2801.apcprd01.prod.exchangelabs.com>

Kushagra Verma <kushagra765@outlook.com> writes:

> Fixed a typo in the word 'concatenated'.
>
> Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
> ---
>  Documentation/admin-guide/bootconfig.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
> index d99994345d41..9355c525fbe0 100644
> --- a/Documentation/admin-guide/bootconfig.rst
> +++ b/Documentation/admin-guide/bootconfig.rst
> @@ -229,7 +229,7 @@ In addition to the kernel command line, the boot config can be used for
>  passing the kernel parameters. All the key-value pairs under ``kernel``
>  key will be passed to kernel cmdline directly. Moreover, the key-value
>  pairs under ``init`` will be passed to init process via the cmdline.
> -The parameters are concatinated with user-given kernel cmdline string
> +The parameters are concatenated with user-given kernel cmdline string
>  as the following order, so that the command line parameter can override
>  bootconfig parameters (this depends on how the subsystem handles parameters
>  but in general, earlier parameter will be overwritten by later one.)::
> -- 
> 2.38.1

Applied, thanks.

jon

      reply	other threads:[~2022-12-03 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 12:22 [PATCH] Documentation: Fixed a typo in bootconfig.rst Kushagra Verma
2022-12-03 10:49 ` Jonathan Corbet [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=87tu2coj7y.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=kushagra765@outlook.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.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