From: Jonathan Corbet <corbet@lwn.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2] printk: Document that CONFIG_BOOT_PRINTK_DELAY required for boot_delay=
Date: Thu, 02 Feb 2023 11:31:51 -0700 [thread overview]
Message-ID: <87wn4zvrzc.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230126225420.1320276-1-helgaas@kernel.org>
Bjorn Helgaas <helgaas@kernel.org> writes:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Document the fact that CONFIG_BOOT_PRINTK_DELAY must be enabled for the
> "boot_delay" kernel parameter to work. Also mention that "lpj=" may be
> necessary.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> Changes from v1 (https://lore.kernel.org/all/20230123180440.901793-1-helgaas@kernel.org/):
> - Clarify use of "lpj=". Reword consequences of delay larger than 10000.
>
> Documentation/admin-guide/kernel-parameters.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 6cfa6e3996cf..814e58487239 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -480,8 +480,10 @@
> See Documentation/block/cmdline-partition.rst
>
> boot_delay= Milliseconds to delay each printk during boot.
> - Values larger than 10 seconds (10000) are changed to
> - no delay (0).
> + Only works if CONFIG_BOOT_PRINTK_DELAY is enabled,
> + and you may also have to specify "lpj=". Boot_delay
> + values larger than 10 seconds (10000) are assumed
> + erroneous and ignored.
> Format: integer
Applied, thanks.
jon
prev parent reply other threads:[~2023-02-02 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 22:54 Bjorn Helgaas
2023-01-27 1:12 ` Randy Dunlap
2023-02-02 18:31 ` 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=87wn4zvrzc.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.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®