From: Andrew Morton <akpm@linux-foundation.org>
To: Li Chen <me@linux.beauty>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Randy Dunlap <rdunlap@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Feng Tang <feng.tang@linux.alibaba.com>,
Kees Cook <kees@kernel.org>, Li RongQing <lirongqing@baidu.com>,
Arnd Bergmann <arnd@arndb.de>,
Frank van der Linden <fvdl@google.com>,
Askar Safin <safinaskar@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Pratyush Yadav <ptyadav@amazon.de>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport (Microsoft) <rppt@kernel.org>
Subject: Re: [PATCH] Documentation: document liveupdate cmdline parameter
Date: Fri, 30 Jan 2026 09:42:37 -0800 [thread overview]
Message-ID: <20260130094237.6f86e3c5c45e2d3443bcce8f@linux-foundation.org> (raw)
In-Reply-To: <20260130112036.359806-1-me@linux.beauty>
On Fri, 30 Jan 2026 19:20:33 +0800 Li Chen <me@linux.beauty> wrote:
> liveupdate is used to enable Live Update Orchestrator (LUO) early during
> boot. Add it to kernel-parameters.txt so users can discover and use it.
>
Thanks,
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3442,6 +3442,11 @@ Kernel parameters
> If there are multiple matching configurations changing
> the same attribute, the last one is used.
>
> + liveupdate= [KNL,EARLY]
> + Format: <bool>
> + Enable Live Update Orchestrator (LUO).
> + Default: off.
> +
> lockd.nlm_grace_period=P [NFS] Assign grace period.
> Format: <integer>
but let's cc the developers:
LIVE UPDATE
M: Pasha Tatashin <pasha.tatashin@soleen.com>
M: Mike Rapoport <rppt@kernel.org>
R: Pratyush Yadav <pratyush@kernel.org>
next prev parent reply other threads:[~2026-01-30 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 11:20 Li Chen
2026-01-30 17:42 ` Andrew Morton [this message]
2026-02-01 4:49 ` Mike Rapoport
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=20260130094237.6f86e3c5c45e2d3443bcce8f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=feng.tang@linux.alibaba.com \
--cc=fvdl@google.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=me@linux.beauty \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=ptyadav@amazon.de \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=safinaskar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome