From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] Please pull u-boot-rockchip
Date: Mon, 7 Jan 2019 13:47:12 -0500 [thread overview]
Message-ID: <20190107184712.GJ5463@bill-the-cat> (raw)
In-Reply-To: <4FEC34C0-516D-4BDE-B736-2056BAE305B4@theobroma-systems.com>
On Sun, Jan 06, 2019 at 03:29:51PM +0100, Philipp Tomsich wrote:
> The following changes since commit 53240275666acf32cb9811e44eaf2fd571a6cb75:
>
> Merge tag 'for-v2019.01' of git://git.denx.de/u-boot-video (2019-01-03 15:34:44 -0500)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-rockchip.git tags/for-master-20190106
>
> for you to fetch changes up to 33502f371d49161a66f7c1f3752dbfc1358129c0:
>
> rockchip: rk3399: fix missing braces in full pinctrl (2019-01-06 15:26:31 +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/20190107/bbf2c61d/attachment.sig>
next prev parent reply other threads:[~2019-01-07 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 14:29 [U-Boot] [PULL] Please pull u-boot-rockchip Philipp Tomsich
2019-01-07 18:47 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-26 7:20 Dr. Philipp Tomsich
2018-04-26 19:11 ` Tom Rini
2018-03-13 22:22 Dr. Philipp Tomsich
2018-03-14 1:30 ` Tom Rini
2018-01-28 16:24 Dr. Philipp Tomsich
2018-01-28 23:25 ` Tom Rini
2017-12-08 13:45 Dr. Philipp Tomsich
2017-12-09 1:34 ` Tom Rini
2017-11-10 13:16 Dr. Philipp Tomsich
2017-11-10 13:19 ` Tom Rini
2017-11-07 8:20 Dr. Philipp Tomsich
2017-11-07 22:29 ` Tom Rini
2017-11-01 10:25 Dr. Philipp Tomsich
2017-11-02 2:19 ` 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=20190107184712.GJ5463@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