public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] Please pull u-boot-rockchip/master
Date: Wed, 3 Jan 2018 20:10:19 -0500	[thread overview]
Message-ID: <20180104011019.GX31350@bill-the-cat> (raw)
In-Reply-To: <3CCE6106-DDB4-4E41-A41D-30ABEC5261B1@theobroma-systems.com>

On Wed, Jan 03, 2018 at 06:07:57PM +0100, Dr. Philipp Tomsich wrote:

> Tom,
> 
> As mentioned earlier, we had another round of last-minute stabilisation fixes in-flight
> for the Rockchip tree.
> 
> Here’s the (hopefully final) pull-request with these fixes for inclusion in 2018.1, which
> includes the following changes:
> (a)	a config adjustment for the RK3368-uQ7 (Lion) board to make sure that the
> 	environment does not run into the TPL stage
> (b)	an additional config option to disable passing a platform-specific parameter
> 	to the ATF (BL31) for backwards-compatibility with some deployed ATF
> 	releases: this affect the Firefly-RK3399 board.
> 
> Thanks,
> Philipp.
> 
> 
> 
> The following changes since commit 1314bd1192b4c67d28bdae7eee639588e88090cd:
> 
>   boards: amlogic: khadas-vim: Typo fixup (2018-01-02 07:57:34 -0500)
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-rockchip.git master
> 
> for you to fetch changes up to e2a75f022d3503b6a5bfcbee660e56383666d107:
> 
>   rockchip: firefly-rk3399: enable SPL_ATF_NO_PLATFORM_PARAM (2018-01-03 14:27:11 +0100)
> 

Applied to u-boot/master, thanks!

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

  parent reply	other threads:[~2018-01-04  1:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 17:07 [U-Boot] [PULL] Please pull u-boot-rockchip/master Dr. Philipp Tomsich
2018-01-03 17:08 ` Dr. Philipp Tomsich
2018-01-04  1:10 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-21  0:00 Dr. Philipp Tomsich
2018-07-21 12:38 ` Tom Rini
2018-05-14 15:32 Dr. Philipp Tomsich
2018-05-14 15:33 ` Dr. Philipp Tomsich
2018-05-15  1:18 ` Tom Rini
2018-02-25 10:43 Dr. Philipp Tomsich
2018-02-26  3:28 ` Tom Rini
2018-02-26  5:05 ` Jonathan Gray
2018-01-01 13:50 Dr. Philipp Tomsich
2018-01-02  0:46 ` Tom Rini
2017-12-18 23:25 Dr. Philipp Tomsich
2017-12-19  1:56 ` Tom Rini
2017-12-01 18:00 Dr. Philipp Tomsich
2017-12-01 21:47 ` Tom Rini
2017-12-01 23:32   ` Dr. Philipp Tomsich
2017-12-02  2:59     ` Tom Rini
2017-11-26 20:42 Dr. Philipp Tomsich
2017-11-27 12:20 ` Tom Rini
2017-09-29 18:14 Dr. Philipp Tomsich
2017-09-29 22:22 ` Tom Rini
2017-09-08 10:15 Dr. Philipp Tomsich
2017-09-08 14:00 ` Tom Rini
2017-09-05  9:25 Dr. Philipp Tomsich
2017-09-06  0:35 ` 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=20180104011019.GX31350@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