From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Please pull mmc-2020-4-22
Date: Wed, 22 Apr 2020 14:34:42 -0400 [thread overview]
Message-ID: <20200422183442.GC4555@bill-the-cat> (raw)
In-Reply-To: <DB6PR0402MB2760E3942675B73F71FB8B1988D20@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Wed, Apr 22, 2020 at 12:29:13PM +0000, Peng Fan wrote:
> Hi Tom,
>
> Please pull mmc-2020-4-22.
>
> I dropped the env patchset from the pull request since delegation change,
> but my CI still have the 3 patches, but without the 3 patches would not
> cause build issue.
>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200422/fa8409df/attachment.sig>
prev parent reply other threads:[~2020-04-22 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 12:29 Please pull mmc-2020-4-22 Peng Fan
2020-04-22 18:34 ` 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=20200422183442.GC4555@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox