From: Weijie Gao <weijie.gao@mediatek.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: <u-boot@lists.denx.de>,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
Tom Rini <trini@konsulko.com>,
"Lucien . Jheng" <lucienzx159@gmail.com>
Subject: Re: [PATCH v3 2/5] misc: fs_loader: allow using long script name in request_firmware_into_buf_via_script()
Date: Thu, 4 Sep 2025 08:23:28 +0800 [thread overview]
Message-ID: <5ada4f98b8d09bd78915bef278dee780de5d7fa2.camel@mediatek.com> (raw)
In-Reply-To: <20250903133600.52169228@karo-electronics.de>
On Wed, 2025-09-03 at 13:36 +0200, Lothar Waßmann wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Hi,
>
> On Wed, 3 Sep 2025 16:38:30 +0800 Weijie Gao wrote:
> > Use cmd_process() to remove the length limit of script name used
> > for
> > run_command().
> >
> > Signed-off-by: Weijie Gao <weijie.gao@mediatek.com>
> > ---
> > drivers/misc/fs_loader.c | 9 +++------
> > 1 file changed, 3 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/misc/fs_loader.c b/drivers/misc/fs_loader.c
> > index 87acd385e23..6a6796c1931 100644
> > --- a/drivers/misc/fs_loader.c
> > +++ b/drivers/misc/fs_loader.c
> > @@ -232,18 +232,15 @@ int request_firmware_into_buf_via_script(void
> > **buf, size_t max_size,
> > const char *script_name,
> > size_t *retsize)
> > {
> > + char *args[2] = { (char *)"run", (char *)script_name };
> >
>
> const char *args[2] = { "run", script_name };
> does not work?
>
> I don't see any need for a non-const 'args' here.
We'll get compiler warning if using const char *[]:
CC drivers/misc/fs_loader.o
drivers/misc/fs_loader.c: In function
'request_firmware_into_buf_via_script':
drivers/misc/fs_loader.c:243:33: warning: passing argument 3 of
'cmd_process' from incompatible pointer type [-Wincompatible-pointer-
types]
243 | ret = cmd_process(0, 2, args, &repeatable, NULL);
| ^~~~
| |
| const char **
In file included from include/image.h:35,
from include/spl.h:17,
from drivers/misc/fs_loader.c:22:
include/command.h:278:64: note: expected 'char * const*' but argument
is of type 'const char **'
278 | enum command_ret_t cmd_process(int flag, int argc, char *const
argv[],
| ~~~~~~~~~~~~
^~~~~~
>
>
> Lothar Waßmann
next prev parent reply other threads:[~2025-09-04 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 8:38 [PATCH v3 0/5] Add support for MediaTek MT7987/MT7988 built-in 2.5Gb ethernet PHY (v3) Weijie Gao
2025-09-03 8:38 ` [PATCH v3 1/5] misc: fs_loader: allow returning actual firmware data size in request_firmware_into_buf_via_script() Weijie Gao
2025-09-03 8:38 ` [PATCH v3 2/5] misc: fs_loader: allow using long script name " Weijie Gao
2025-09-03 11:36 ` Lothar Waßmann
2025-09-04 0:23 ` Weijie Gao [this message]
2025-09-04 9:28 ` Lothar Waßmann
2025-09-05 1:26 ` Weijie Gao
2025-09-05 5:35 ` Lothar Waßmann
2025-09-03 8:38 ` [PATCH v3 3/5] net: mediatek: associate PHY device with dts node specified by phy-handle Weijie Gao
2025-09-03 8:38 ` [PATCH v3 4/5] net: phy: Add MediaTek built-in 2.5Gb ethernet PHY driver Weijie Gao
2025-09-03 8:38 ` [PATCH v3 5/5] MAINTAINERS: update ethernet-related file list for MediaTek ARM platform Weijie Gao
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=5ada4f98b8d09bd78915bef278dee780de5d7fa2.camel@mediatek.com \
--to=weijie.gao@mediatek.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=LW@KARO-electronics.de \
--cc=lucienzx159@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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