From: Tom Rini <trini@konsulko.com>
To: "Chee, Tien Fong" <tien.fong.chee@altera.com>
Cc: U-Boot Mailing List <u-boot@lists.u-boot-project.org>,
Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>,
Dinesh Maniyam <dinesh.maniyam@altera.com>,
Chen Huei Lok <chen.huei.lok@altera.com>,
Brian Sune <briansune@gmail.com>,
Tze Yee Ng <tzeyee.ng@altera.com>, Peng Fan <peng.fan@nxp.com>,
Naresh Kumar Ravulapalli <nareshkumar.ravulapalli@altera.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Boon Khai Ng <boon.khai.ng@altera.com>
Subject: Re: [GIT PULL] SoCFPGA updates for next (2026-08-17)
Date: Mon, 17 Aug 2026 12:27:35 -0600 [thread overview]
Message-ID: <20260817182735.GQ3297518@bill-the-cat> (raw)
In-Reply-To: <cfa5d305-908e-4ab5-8725-47f287fb5e54@altera.com>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Mon, Aug 17, 2026 at 11:29:50AM +0800, Chee, Tien Fong wrote:
> Hi Tom,
>
> Please pull the following SoCFPGA updates for next.
>
> The following changes since commit 527115ef6783cec49e5610c523c124b399011361:
>
> pylibfdt: Replace removed SWIG Python 2 compatibility macros (2026-08-13
> 10:12:41 -0600)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-socfpga.git
> tags/u-boot-socfpga-next-20260817
Can you please put this on git.u-boot-project.org? The denx gitlab is
unresponsive at this point for me, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-17 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 3:29 [GIT PULL] SoCFPGA updates for next (2026-08-17) Chee, Tien Fong via U-Boot
2026-08-17 18:27 ` Tom Rini [this message]
2026-08-18 4:04 ` Chee, Tien Fong
2026-08-18 16:32 ` Chee, Tien Fong
2026-08-18 16:35 ` Tom Rini
2026-08-18 20:17 ` Tom Rini
2026-08-19 1:16 ` Chee, Tien Fong
2026-08-19 18:22 ` 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=20260817182735.GQ3297518@bill-the-cat \
--to=trini@konsulko.com \
--cc=alif.zakuan.yuslaimi@altera.com \
--cc=boon.khai.ng@altera.com \
--cc=briansune@gmail.com \
--cc=chen.huei.lok@altera.com \
--cc=dinesh.maniyam@altera.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=nareshkumar.ravulapalli@altera.com \
--cc=peng.fan@nxp.com \
--cc=tien.fong.chee@altera.com \
--cc=tzeyee.ng@altera.com \
--cc=u-boot@lists.u-boot-project.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