From: Leo Liang <ycliang@andestech.com>
To: Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>,
<heinrich.schuchardt@canonical.com>, <ben.dooks@codethink.co.uk>,
<jamie.gibbons@microchip.com>, <sputnik@on-the-web.ch>,
<michal.simek@amd.com>
Subject: Re: [GIT PULL] u-boot-riscv/master
Date: Wed, 13 Aug 2025 14:57:10 +0800 [thread overview]
Message-ID: <aJw3OPPRV8ZZosNR@swlinux02> (raw)
In-Reply-To: <20250812152224.GT124814@bill-the-cat>
On Tue, Aug 12, 2025 at 09:22:24AM -0600, Tom Rini wrote:
> [EXTERNAL MAIL]
> Date: Tue, 12 Aug 2025 09:22:24 -0600
> From: Tom Rini <trini@konsulko.com>
> To: Leo Liang <ycliang@andestech.com>
> Cc: u-boot@lists.denx.de, rick@andestech.com,
> heinrich.schuchardt@canonical.com, ben.dooks@codethink.co.uk,
> jamie.gibbons@microchip.com, sputnik@on-the-web.ch, michal.simek@amd.com
> Subject: Re: [GIT PULL] u-boot-riscv/master
>
> On Tue, Aug 12, 2025 at 04:04:49PM +0800, Leo Liang wrote:
>
> > Hi Tom,
> >
> > The following changes since commit acfacf452441d0a659e3afbd55fd6061aa17e647:
> >
> > Prepare v2025.10-rc2 (2025-08-11 13:47:46 -0600)
> >
> > are available in the Git repository at:
> >
> > https://source.denx.de/u-boot/custodians/u-boot-riscv.git
> >
> > for you to fetch changes up to bddcd6bcba081aaaaafe30d1b8f9f3c83f069bde:
> >
> > starfive: fix return code of `mac write_eeprom` (2025-08-12 15:34:39 +0800)
> >
> > CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/27348
> > ----------------------------------------------------------------
> > - Board: mbv: Prepare MBV for CI
> > - Board: MPFS Icicle Kit cleanup
> > - Board: Add Andes Voyager board support
> > - RISCV: Update SYS_BOOTM_LEN to commonly used value
> > - starfive: fix return code of `mac write_eeprom`
>
> So, there's a few problems here. First, checkpatch.pl finds spacing and
> spelling issues, which I would normally just fixup in place. But second,
> voyager_spl doesn't build:
> riscv64: + voyager_spl
> +(voyager_spl) In file included from include/linux/printk.h:4,
> +(voyager_spl) from include/linux/kernel.h:5,
> +(voyager_spl) from include/linux/libfdt_env.h:13,
> +(voyager_spl) from include/linux/libfdt.h:6,
> +(voyager_spl) from include/fdtdec.h:17,
> +(voyager_spl) from include/dm/ofnode.h:11,
> +(voyager_spl) from include/dm/device.h:13,
> +(voyager_spl) from include/dm.h:13,
> +(voyager_spl) from common/spl/spl.c:13:
> +(voyager_spl) common/spl/spl.c: In function 'spl_set_header_raw_uboot':
> +(voyager_spl) common/spl/spl.c:281:27: error: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'long int' [-Werror=format=]
> +(voyager_spl) 281 | log_debug("Default load addr %x (u_boot_pos=%lx)\n",
> +(voyager_spl) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +(voyager_spl) include/log.h:234:24: note: in definition of macro 'log'
> +(voyager_spl) 234 | printf(_fmt, ##_args); \
> +(voyager_spl) | ^~~~
> +(voyager_spl) common/spl/spl.c:281:17: note: in expansion of macro 'log_debug'
> +(voyager_spl) | ^~~~~~~~~
> +(voyager_spl) common/spl/spl.c:281:47: note: format string is defined here
> +(voyager_spl) | ~^
> +(voyager_spl) | |
> +(voyager_spl) | unsigned int
> +(voyager_spl) | %lx
> +(voyager_spl) cc1: all warnings being treated as errors
> +(voyager_spl) make[3]: *** [scripts/Makefile.build:296: spl/common/spl/spl.o] Error 1
> +(voyager_spl) make[2]: *** [scripts/Makefile.xpl:547: spl/common/spl] Error 2
> +(voyager_spl) make[1]: *** [Makefile:2358: spl/u-boot-spl] Error 2
> +(voyager_spl) make: *** [Makefile:198: sub-make] Error 2
>
> Please fix and re-submit, thanks.
Hi Tom,
Sorry! I will fix these and re-submit ASAP.
Best regards,
Leo
>
> --
> Tom
next prev parent reply other threads:[~2025-08-13 6:58 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:04 [GIT PULL] u-boot-riscv/master Leo Liang
2025-08-12 15:22 ` Tom Rini
2025-08-13 6:57 ` Leo Liang [this message]
2025-08-13 11:16 ` Martin Herren
2025-08-13 11:59 ` Leo Liang
-- strict thread matches above, loose matches on Subject: below --
2025-10-16 12:07 [GIT,PULL] u-boot-riscv/master Leo Liang
2025-10-16 17:38 ` Tom Rini
2025-05-21 9:50 [GIT PULL] u-boot-riscv/master Leo Liang
2025-05-21 18:39 ` Tom Rini
2025-05-22 11:28 ` Conor Dooley
2025-05-22 14:45 ` Tom Rini
2025-05-22 15:36 ` Leo Liang
2025-05-22 15:54 ` Tom Rini
2025-05-22 16:40 ` Yao Zi
2025-05-23 9:18 ` Conor Dooley
2025-05-26 3:32 ` Mayuresh Chitale
2025-05-26 9:17 ` Conor Dooley
2025-05-26 14:56 ` Tom Rini
2025-05-26 17:34 ` Mayuresh Chitale
2025-05-26 18:16 ` Tom Rini
2025-05-27 17:10 ` Mayuresh Chitale
2025-05-27 17:34 ` Tom Rini
2025-04-25 10:07 Leo Liang
2025-04-25 10:35 ` Yao Zi
2025-04-26 14:14 ` Tom Rini
2025-04-25 12:57 ` E Shattow
2025-04-25 13:02 ` E Shattow
2025-04-25 23:43 ` Tom Rini
2025-04-26 1:13 ` E Shattow
2025-04-26 14:14 ` Tom Rini
2025-04-27 7:47 ` E Shattow
2025-03-25 6:19 Leo Liang
2025-03-25 20:18 ` Tom Rini
2025-03-06 12:18 Leo Liang
2025-03-07 11:20 ` Yao Zi
2025-02-20 5:13 Leo Liang
2025-02-20 17:19 ` Tom Rini
2025-02-03 8:17 Leo Liang
2025-02-03 21:26 ` Tom Rini
2025-01-17 1:53 Leo Liang
2025-01-17 17:56 ` Tom Rini
2024-11-27 13:08 Leo Liang
2024-11-27 18:54 ` Tom Rini
2024-11-06 12:12 Leo Liang
2024-11-08 16:51 ` Tom Rini
2024-11-11 13:24 ` Tom Rini
2024-10-29 12:33 Leo Liang
2024-10-29 16:37 ` Tom Rini
2024-10-28 12:24 Leo Liang
2024-10-28 19:33 ` Tom Rini
2024-07-22 8:29 Leo Liang
2024-07-22 19:31 ` Tom Rini
2024-05-30 8:56 Leo Liang
2024-06-03 17:42 ` Tom Rini
2024-05-14 13:28 Leo Liang
2024-05-14 16:14 ` Tom Rini
2024-05-01 16:38 Leo Liang
2024-05-02 14:42 ` Tom Rini
2024-04-09 8:25 Leo Liang
2024-04-10 0:43 ` Tom Rini
2024-03-26 13:22 Leo Liang
2024-03-27 12:12 ` Tom Rini
2024-03-12 8:51 Leo Liang
2024-03-12 18:52 ` Tom Rini
2024-01-31 10:21 Leo Liang
2024-01-31 14:14 ` Tom Rini
2023-12-14 2:38 Leo Yu-Chi Liang(梁育齊)
2023-12-14 12:19 ` Tom Rini
2023-12-14 12:46 ` Leo Liang
2023-12-14 14:39 ` Tom Rini
2023-12-07 13:46 Leo Liang
2023-12-09 20:59 ` Tom Rini
2023-11-02 10:49 Leo Liang
2023-11-02 14:53 ` Tom Rini
2021-02-26 1:53 Leo Liang
2021-02-26 17:40 ` Tom Rini
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=aJw3OPPRV8ZZosNR@swlinux02 \
--to=ycliang@andestech.com \
--cc=ben.dooks@codethink.co.uk \
--cc=heinrich.schuchardt@canonical.com \
--cc=jamie.gibbons@microchip.com \
--cc=michal.simek@amd.com \
--cc=rick@andestech.com \
--cc=sputnik@on-the-web.ch \
--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 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.