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.07-rc5
Date: Fri, 11 Jun 2021 08:28:28 -0400 [thread overview]
Message-ID: <20210611122828.GR9516@bill-the-cat> (raw)
In-Reply-To: <f3722793-8b3f-2cd9-7294-6e060ca290d1@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
On Fri, Jun 11, 2021 at 01:20:15PM +0200, Michal Simek wrote:
> Hi Tom,
>
> please pull these 3 fixes to your tree. When are you plan to open next
> branch?
The next branch is open now, I thought I mentioned that in the last -rc
email but I didn't send a separate one like I had in the past, so, I'll
do that in a moment.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-06-11 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 11:20 [GIT PULL] xilinx patches for v2021.07-rc5 Michal Simek
2021-06-11 12:28 ` Tom Rini [this message]
2021-06-13 21:32 ` 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=20210611122828.GR9516@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;
as well as URLs for NNTP newsgroup(s).