All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Tom Rini <trini@konsulko.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: [GIT PULL] AMD/Xilinx changes for 2026-01-rc3
Date: Wed, 19 Nov 2025 13:52:19 +0100	[thread overview]
Message-ID: <faafa443-e804-4506-ac4a-658c2b8cc339@amd.com> (raw)

Hi Tom,

please pull these two fixes to your tree. In CI docs part is failing but it has 
nothing to do with below patches.
https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/pipelines/28413

Thanks,
Michal


The following changes since commit c2b25f8f66a31e3fe435c93c4339f95ab4c24b9b:

   mailmap: Add entry for Sam Protsenko (2025-11-18 15:55:01 -0600)

are available in the Git repository at:

   https://source.denx.de/u-boot/custodians/u-boot-microblaze.git 
tags/xilinx-for-v2026.01-rc3

for you to fetch changes up to 2e86581d055bff8335d7e43d58617db16f11384f:

   net: axi_emac: Fix compilation warnings (2025-11-19 09:28:50 +0100)

----------------------------------------------------------------
AMD/Xilinx/FPGA changes for v2026.01-rc3

- Align brcp1 boot.bin location
- Fix MB-V compilation warning when AXI enet is enabled

----------------------------------------------------------------
Sai Varun Venkatapuram (1):
       net: axi_emac: Fix compilation warnings

Wolfgang Wallner (1):
       arm: dts: brcp1: Move SPL partition to offset 0x8000 in SPI flash

  arch/arm/dts/zynq-binman-brcp1.dtsi |  2 +-
  drivers/net/xilinx_axi_emac.c       | 16 ++++++++--------
  2 files changed, 9 insertions(+), 9 deletions(-)

             reply	other threads:[~2025-11-19 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 12:52 Michal Simek [this message]
2025-11-19 14:19 ` [GIT PULL] AMD/Xilinx changes for 2026-01-rc3 Tom Rini
2025-11-19 16:33 ` 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=faafa443-e804-4506-ac4a-658c2b8cc339@amd.com \
    --to=michal.simek@amd.com \
    --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.