From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Please pull u-boot-dm/next into -next
Date: Fri, 26 Mar 2021 15:14:32 -0400 [thread overview]
Message-ID: <20210326191432.GK1310@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0_ACioniN1vpEGL4uoz4F7FAmfXb_6T0RBSgTqrV3CwQ@mail.gmail.com>
On Fri, Mar 26, 2021 at 07:05:43PM +1300, Simon Glass wrote:
> Hi Tom,
>
> Well here we are again...let's see how this one fares.
>
> This is for the -next branch.
>
>
> https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/6933
>
>
> The following changes since commit 874dcedee92a828b03c8d3146dccfaa8b709618b:
>
> Merge branch '2021-03-20-mediatek-updates' into next (2021-03-20
> 19:27:22 -0400)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-dm.git tags/dm-pull-26mar21-take2
>
> for you to fetch changes up to fcae6682a7929abf88d9f0b756f9d5f9725e4d14:
>
> binman: Update various pieces of the documentation (2021-03-26 17:03:10 +1300)
>
Applied to u-boot/next, 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/20210326/ec072ece/attachment.sig>
next prev parent reply other threads:[~2021-03-26 19:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 6:05 Please pull u-boot-dm/next into -next Simon Glass
2021-03-26 19:14 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-20 20:58 Simon Glass
2021-03-20 23:21 ` Marek Behún
2021-03-21 0:20 ` Simon Glass
2021-03-21 1:16 ` Bin Meng
2021-03-21 1:18 ` Simon Glass
2021-03-21 1:20 ` Tom Rini
2021-01-06 2:53 Simon Glass
2021-01-06 12:56 ` Tom Rini
2020-12-23 19:04 Simon Glass
2020-12-24 14:12 ` Tom Rini
2020-12-14 15:50 Simon Glass
2020-12-15 14:06 ` Tom Rini
2020-12-15 16:28 ` Simon Glass
2020-12-17 2:10 ` Simon Glass
2020-12-17 14:01 ` 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=20210326191432.GK1310@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.