From: E Shattow <e@freeshell.de>
To: Tom Rini <trini@konsulko.com>, Leo Liang <ycliang@andestech.com>,
Yao Zi <ziyao@disroot.org>
Cc: u-boot@lists.denx.de, rick@andestech.com, randolph@andestech.com,
hal.feng@starfivetech.com, jamie.gibbons@microchip.com,
eoin.dickson@microchip.com, wangruikang@iscas.ac.cn,
greentime.hu@sifive.com, Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [GIT,PULL] u-boot-riscv/next
Date: Wed, 24 Sep 2025 19:07:22 -0700 [thread overview]
Message-ID: <1871663e-b918-4351-9e9e-97f9a4c73733@freeshell.de> (raw)
In-Reply-To: <175839044541.1370912.7338002899133591795.b4-ty@konsulko.com>
Hi Tom, Leo, and Yao,
On 9/20/25 10:47, Tom Rini wrote:
> On Sat, 20 Sep 2025 18:20:01 +0800, Leo Liang wrote:
>
>> The following changes since commit a209627ed7921f40669f5c0795570d40e77e4cb7:
>>
>> Merge patch series "board: dhelectronics: Check pointer before access in dh_get_value_from_eeprom_buffer()" (2025-09-16 16:14:30 -0600)
>>
>> are available in the Git repository at:
>>
>> https://source.denx.de/u-boot/custodians/u-boot-riscv.git next
>>
>> [...]
>
> Merged into u-boot/next, thanks!
>
Runtime regression for VisionFive2 SPL bisected to bad commit
a681cfecb434 "riscv: Add a Zalrsc-only alternative for synchronization
in start.S". Confirmed by checking out origin/next (to 44c4919e9 "test:
Fix optee unit test") and reverting that commit a681cfecb434 only.
I am late to testing this, sorry about that. It would have been better
to catch this before becoming part of a range of bisect commits that now
have a non-functional SPL on visionfive2.
Best regards,
-E
next prev parent reply other threads:[~2025-09-25 2:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 10:20 [GIT,PULL] u-boot-riscv/next Leo Liang
2025-09-20 17:47 ` Tom Rini
2025-09-25 2:07 ` E Shattow [this message]
2025-09-25 3:39 ` E Shattow
2025-09-25 4:57 ` Yao Zi
2025-09-25 6:36 ` E Shattow
-- strict thread matches above, loose matches on Subject: below --
2026-03-17 6:01 [GIT PULL] u-boot-riscv/next Leo Yu-Chi Liang
2026-03-18 17:05 ` Tom Rini
2026-03-23 19:20 ` E Shattow
2026-03-23 20:07 ` Tom Rini
2026-03-13 2:06 [GIT,PULL] u-boot-riscv/next Leo Liang
2026-03-13 16:52 ` Tom Rini
2026-03-13 22:59 ` E Shattow
2026-03-16 12:23 ` Leo Liang
2025-12-08 6:19 [GIT PULL] u-boot-riscv/next Leo Liang
2025-12-08 22:09 ` Tom Rini
2025-07-03 14:09 Leo Liang
2025-07-03 16:29 ` Tom Rini
2025-03-25 10:55 Leo Liang
2025-03-25 20:17 ` Tom Rini
2024-12-18 7:49 Leo Liang
2024-12-18 17:40 ` Tom Rini
2024-10-28 12:25 Leo Liang
2024-10-28 15:20 ` Tom Rini
2024-10-29 9:35 ` Leo Liang
2024-10-29 13:01 ` Michal Simek
2023-12-28 5:38 Leo Liang
2023-12-28 16:55 ` Tom Rini
2023-12-18 11:44 Leo Liang
2023-12-18 16:59 ` 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=1871663e-b918-4351-9e9e-97f9a4c73733@freeshell.de \
--to=e@freeshell.de \
--cc=eoin.dickson@microchip.com \
--cc=greentime.hu@sifive.com \
--cc=hal.feng@starfivetech.com \
--cc=jamie.gibbons@microchip.com \
--cc=randolph@andestech.com \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wangruikang@iscas.ac.cn \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.com \
--cc=ziyao@disroot.org \
/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