From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] Rockchip dts32 updates for 4.13 part1
Date: Sun, 18 Jun 2017 19:07:54 -0700 [thread overview]
Message-ID: <20170619020754.GL30022@localhost> (raw)
In-Reply-To: <2090243.QTRV0U63fj@phil>
On Fri, Jun 09, 2017 at 12:13:44PM +0200, Heiko Stuebner wrote:
> Hi Arnd, Kevin, Olof,
>
> please find below and in the subsequent replies Rockchip-related changes
> for 4.13. The tags describe the individual changes, but hightlight are probably
> the Mali-Midgard nodes on rk3288 and rk3399-Firefly board.
>
> So if nothing looks out of place, please pull.
>
> Thanks
> Heiko
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.13-rockchip-dts32-1
>
> for you to fetch changes up to 81b61d37705173b8b9eb52c4566a8fc7c7099520:
>
> ARM: dts: rockchip: enable usb for rk3229 evb board (2017-06-02 14:11:57 +0200)
>
> ----------------------------------------------------------------
> A bunch of changes including mali gpu nodes for rk3288 boards
> following (and including) the new Mali Midgard binding; a lot of
> improvements for the rk3228/rk3229 socs (tsadc, operating points,
> usb, clock-rates, pinctrl, watchdog); finalizing the rk1108->rv1108
> rename and adc buttons for the rk3288 firefly boards.
Thanks, merged.
-Olof
prev parent reply other threads:[~2017-06-19 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 10:13 [GIT PULL 1/3] Rockchip dts32 updates for 4.13 part1 Heiko Stuebner
2017-06-09 10:14 ` [GIT PULL 2/3] Rockchip dts64 " Heiko Stuebner
2017-06-19 2:08 ` Olof Johansson
2017-06-09 10:15 ` [GIT PULL 3/3] Rockchip soc32 " Heiko Stuebner
2017-06-19 2:08 ` Olof Johansson
2017-06-19 2:07 ` Olof Johansson [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=20170619020754.GL30022@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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).