From: "Chee, Tien Fong" <tien.fong.chee@altera.com>
To: Tom Rini <trini@konsulko.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: Tue, 18 Aug 2026 12:04:38 +0800 [thread overview]
Message-ID: <e29102bb-10bd-48d7-ad6b-24fa5d430ebb@altera.com> (raw)
In-Reply-To: <20260817182735.GQ3297518@bill-the-cat>
Hi Tom,
On 18/8/2026 2:27 am, Tom Rini wrote:
> 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.
Could you please approve my access/login for git.u-boot-project.org?
I need access to help publish/pull the SoCFPGA updates, and I'm
currently unable to proceed.
Thanks,
Tien Fong
next prev parent reply other threads:[~2026-08-18 4:04 UTC|newest]
Thread overview: 7+ 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
2026-08-18 4:04 ` Chee, Tien Fong [this message]
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
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=e29102bb-10bd-48d7-ad6b-24fa5d430ebb@altera.com \
--to=tien.fong.chee@altera.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=trini@konsulko.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 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.