All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Xilinx/FPGA patches for v2020.01
Date: Fri, 11 Oct 2019 10:56:52 -0400	[thread overview]
Message-ID: <20191011145652.GC16029@bill-the-cat> (raw)
In-Reply-To: <6b2f1b4a-c0e1-ac0f-adf8-740f67ac61cd@monstr.eu>

On Wed, Oct 09, 2019 at 12:30:36PM +0200, Michal Simek wrote:

> Hi Tom,
> 
> please pull the following changes to your tree. I have also included
> trivial patch for apalis board. Networking stuff have been assigned to
> me in patchwork that's why I am also including them.
> 
> Gitlab CI failed but it is related to file path we discussed already.
> https://gitlab.denx.de/u-boot/custodians/u-boot-microblaze/pipelines/879
> 
> I expect when you merge this to your branch all will pass.
> 
> Thanks,
> Michal
> 
> The following changes since commit 61ba1244b548463dbfb3c5285b6b22e7c772c5bd:
> 
>   Prepare v2019.10 (2019-10-07 17:14:02 -0400)
> 
> are available in the Git repository at:
> 
>   git at gitlab.denx.de:u-boot/custodians/u-boot-microblaze.git
> tags/xilinx-for-v2020.01
> 
> for you to fetch changes up to bcaa0e3302e384ad65c352b385678acdf3f20c0a:
> 
>   arm64: versal: remove debug uart for versal virt (2019-10-08 13:14:54
> +0200)
> 

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191011/ca4e4faf/attachment.sig>

      reply	other threads:[~2019-10-11 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 10:30 [U-Boot] [GIT PULL] Xilinx/FPGA patches for v2020.01 Michal Simek
2019-10-11 14:56 ` Tom Rini [this message]

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=20191011145652.GC16029@bill-the-cat \
    --to=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.