All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Breno Leitao" <leitao@debian.org>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v6 6/8] Documentation: bootconfig: document build-time cmdline rendering
Date: Tue, 23 Jun 2026 16:27:58 +0000	[thread overview]
Message-ID: <20260623162759.25BA51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260623-bootconfig_using_tools-v6-6-640c2f587a3c@debian.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The documentation for CONFIG_CMDLINE_FROM_BOOTCONFIG omits the Kconfig requirement that CONFIG_CMDLINE must be empty.
--

commit 7ac5b833fb6889abf419a5e5890a63a00f59d74e
Author: Breno Leitao <leitao@debian.org>

Documentation: bootconfig: document build-time cmdline rendering

This commit adds documentation describing the CONFIG_CMDLINE_FROM_BOOTCONFIG
option, explaining its build-time rendering behavior, requirements, opt-in
semantics, and how it interacts with other command line sources.

> diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
> index f712758472d5c..349cefbb2bbcd 100644
> --- a/Documentation/admin-guide/bootconfig.rst
> +++ b/Documentation/admin-guide/bootconfig.rst
[ ... ]
> +``CONFIG_CMDLINE_FROM_BOOTCONFIG`` resolves this by rendering the
> +``kernel`` subtree of ``CONFIG_BOOT_CONFIG_EMBED_FILE`` into a flat cmdline
> +string at kernel build time (via ``tools/bootconfig -C``) and prepending
> +it to ``boot_command_line`` during early architecture setup, so the keys
> +are visible to ``parse_early_param()``.
> +
> +The option requires ``CONFIG_BOOT_CONFIG_EMBED=y``, a non-empty
> +``CONFIG_BOOT_CONFIG_EMBED_FILE``, and an architecture that selects
> +``CONFIG_ARCH_SUPPORTS_CMDLINE_FROM_BOOTCONFIG``. Currently only x86

[Severity: Low]
Should this also mention the requirement that CONFIG_CMDLINE must be empty?

Users might satisfy all the explicitly listed requirements but still find the
option hidden in menuconfig if their kernel is configured with a non-empty
built-in command line, because the Kconfig rule uses depends on CMDLINE = "".

> +selects it; on other architectures the embedded bootconfig still works,
> +but only through the late runtime parser.
> +
> +The same ``bootconfig`` opt-in applies as elsewhere: the rendered keys
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260623-bootconfig_using_tools-v6-0-640c2f587a3c@debian.org?part=6

  reply	other threads:[~2026-06-23 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 16:15 [PATCH v6 0/8] bootconfig: embed kernel.* cmdline at build time Breno Leitao
2026-06-23 16:15 ` [PATCH v6 1/8] bootconfig: fix NULL-pointer arithmetic in xbc_snprint_cmdline() Breno Leitao
2026-06-23 16:15 ` [PATCH v6 2/8] bootconfig: render descendant keys when xbc_snprint_cmdline() root has a value Breno Leitao
2026-06-23 16:15 ` [PATCH v6 3/8] bootconfig: render embedded bootconfig as a kernel cmdline at build time Breno Leitao
2026-06-23 16:15 ` [PATCH v6 4/8] bootconfig: clean build-time tools/bootconfig from make clean Breno Leitao
2026-06-23 16:15 ` [PATCH v6 5/8] bootconfig: add xbc_prepend_embedded_cmdline() helper Breno Leitao
2026-06-23 16:15 ` [PATCH v6 6/8] Documentation: bootconfig: document build-time cmdline rendering Breno Leitao
2026-06-23 16:27   ` sashiko-bot [this message]
2026-06-23 16:15 ` [PATCH v6 7/8] bootconfig: skip runtime kernel.* render once prepended early Breno Leitao
2026-06-23 16:15 ` [PATCH v6 8/8] x86/setup: prepend embedded bootconfig cmdline before parse_early_param Breno Leitao

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=20260623162759.25BA51F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=leitao@debian.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.