Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Wilson Felipe Pereira <wfelipe@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	linux-arch@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/3] init/Kconfig: generalize config COMMAND_LINE_SIZE
Date: Thu, 6 Aug 2026 15:57:46 -0700	[thread overview]
Message-ID: <20260806155746.0c3590dc2f3228e7d65e986c@linux-foundation.org> (raw)
In-Reply-To: <20260806061429.474992-1-wfelipe@google.com>

On Thu,  6 Aug 2026 06:14:13 +0000 Wilson Felipe Pereira <wfelipe@google.com> wrote:

> This patch series promotes COMMAND_LINE_SIZE from arch/s390/Kconfig to
> init/Kconfig to be generally available to other architectures.
> 
> In some use cases, such as netboot kernels, rootfs configurations, larger
> initramfs setups, require larger sizes. While for embedded workloads, it
> can be reduced to save memory.
> 
> Since COMMAND_LINE_SIZE can be larger, it also makes sense to allow
> INIT_ENV_ARG_LIMIT to be configured.

Thanks.

AI review pointed at a few possible issues - I eyeballed a couple and
they appear significant.
	https://sashiko.dev/#/patchset/20260806061429.474992-1-wfelipe@google.com


> Originally-by: Maciej Żenczykowski <maze@google.com>

fyi, it's minor, but Originally-by: isn't actually a thing.  It's
mentioned in the -tip documentation, nothing else endorses it.

I have no issue with it but formally these patches should also have
Maciej's Signed-off-by: 


Please let's target 7.3-rc1 for these changes - I'm deep into
stem-the-flood mode for this -rc cycle.


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-08-06 22:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  6:14 [PATCH 0/3] init/Kconfig: generalize config COMMAND_LINE_SIZE Wilson Felipe Pereira
2026-08-06  6:14 ` [PATCH 1/3] init/Kconfig: generalize config COMMAND_LINE_SIZE to all architectures Wilson Felipe Pereira
2026-08-06  6:14 ` [PATCH 2/3] arch: use CONFIG_COMMAND_LINE_SIZE across " Wilson Felipe Pereira
2026-08-06  6:14 ` [PATCH 3/3] init/Kconfig: make config INIT_ENV_ARG_LIMIT user-configurable Wilson Felipe Pereira
2026-08-06 22:57 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-06  6:05 [PATCH 0/3] init/Kconfig: generalize config COMMAND_LINE_SIZE Wilson Felipe Pereira

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=20260806155746.0c3590dc2f3228e7d65e986c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=agordeev@linux.ibm.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=wfelipe@google.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