From: Leo Liang <ycliang@andestech.com>
To: E Shattow <e@freeshell.de>
Cc: Tom Rini <trini@konsulko.com>, <u-boot@lists.denx.de>,
<rick@andestech.com>, <nick.hu@sifive.com>, <jimmy.ho@sifive.com>,
<schwab@suse.de>, Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [GIT,PULL] u-boot-riscv/next
Date: Mon, 16 Mar 2026 20:23:31 +0800 [thread overview]
Message-ID: <abf2QyGifRhAs9yI@swlinux02> (raw)
In-Reply-To: <5cbcf317-f36e-4c57-9a97-0b5f27bf17df@freeshell.de>
On Fri, Mar 13, 2026 at 03:59:59PM -0700, E Shattow wrote:
> [EXTERNAL MAIL]
>
> Hi Leo, and Tom,
>
> On 3/13/26 09:52, Tom Rini wrote:
> > On Fri, 13 Mar 2026 10:06:24 +0800, Leo Liang wrote:
> >
> >> The following changes since commit 8bc2a5196c1c0bb5dbdaca073323da0015a0de37:
> >>
> >> arm: k3: Kconfig: Enable fTPM and RPMB support (2026-03-10 12:35:18 -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!
> >
>
> Did we get a resolution on applying Hal's series to add support for
> VisionFive 2 Lite ? ref.:
> https://lore.kernel.org/u-boot/20260214145634.GQ2747538@bill-the-cat/
>
> -E
Hi E,
The previous mistake was made when resolving the conflicts.
I am preparing PRs now for all the "board support" patchsets,
and still see some minor issues.
I will send out those PRs once the issues are resolved.
Thanks for the reminder!
Best regards,
Leo
next prev parent reply other threads:[~2026-03-16 12:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- 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
2025-12-08 6:19 Leo Liang
2025-12-08 22:09 ` Tom Rini
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
2025-09-25 3:39 ` E Shattow
2025-09-25 4:57 ` Yao Zi
2025-09-25 6:36 ` E Shattow
2025-07-03 14:09 [GIT PULL] u-boot-riscv/next 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=abf2QyGifRhAs9yI@swlinux02 \
--to=ycliang@andestech.com \
--cc=e@freeshell.de \
--cc=jimmy.ho@sifive.com \
--cc=nick.hu@sifive.com \
--cc=rick@andestech.com \
--cc=schwab@suse.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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.