From: Paul Walmsley <pjw@kernel.org>
To: Austin Kim <austindh.kim@gmail.com>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: increase COMMAND_LINE_SIZE value to 2048
Date: Thu, 12 Feb 2026 17:52:25 -0700 (MST) [thread overview]
Message-ID: <55cbf9fb-6d13-a893-e8b0-429fe972e207@kernel.org> (raw)
In-Reply-To: <aW3gFmOlA/Z4kmfJ@adminpc-PowerEdge-R7525>
On Mon, 19 Jan 2026, Austin Kim wrote:
> From: Austin Kim <austin.kim@lge.com>
>
> SoC people may send many parameters to configure the drivers via kernel
> command line. If COMMAND_LINE_SIZE is not enough, they may go through
> unexpected error.
>
> To avoid the potential pain, we had better increase COMMAND_LINE_SIZE.
>
> Signed-off-by: Austin Kim <austin.kim@lge.com>
Thanks, queued for v7.1.
- Paul
next prev parent reply other threads:[~2026-02-13 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:41 [PATCH] riscv: increase COMMAND_LINE_SIZE value to 2048 Austin Kim
2026-02-13 0:52 ` Paul Walmsley [this message]
2026-02-13 1:18 ` Austin Kim
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=55cbf9fb-6d13-a893-e8b0-429fe972e207@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=austindh.kim@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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