From: Tom Rini <trini@konsulko.com>
To: Michal Simek <monstr@monstr.eu>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [GIT PULL] xilinx patches for v2021.10
Date: Thu, 1 Jul 2021 16:10:32 -0400 [thread overview]
Message-ID: <20210701201032.GO9516@bill-the-cat> (raw)
In-Reply-To: <f6c96836-5313-789e-a12a-ad0073a0ebe8@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Thu, Jul 01, 2021 at 11:25:22AM +0200, Michal Simek wrote:
> Hi,
>
> please pull these patches to your tree (next). There are a lot of DT
> syncup changes which are also going to Linux kernel.
> CI loop doesn't show any problem.
>
> BTW: Isn't there any option in CI not to run builds against the same
> sha1? Because I see build for the branch itself and then for the tag
> which is kind of wasting of resources.
I don't know of one for GitLab, but I've not checked. Azure is smarter
about this and doesn't.
>
> Thanks,
> Michal
>
>
> The following changes since commit 1ce892cb1ce970d8ee6ffcecc22351c84e67fca4:
>
> azure: Use msys2 20210604 installer for Windows build (2021-06-22
> 09:06:03 -0400)
>
> are available in the Git repository at:
>
> git@source.denx.de:u-boot/custodians/u-boot-microblaze.git
> tags/xilinx-for-v2021.10
>
> for you to fetch changes up to 45576273e9209309238f332c85a6fef955c49b59:
>
> xilinx: zynqmp: Add support for 67dr silicon (2021-07-01 09:25:06 +0200)
>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2021-07-01 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 9:25 [GIT PULL] xilinx patches for v2021.10 Michal Simek
2021-07-01 20:10 ` 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=20210701201032.GO9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=monstr@monstr.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox