From: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [GIT PULL 1/3] Rockchip dts32 updates for 5.3 round 1
Date: Wed, 19 Jun 2019 06:22:31 -0700 [thread overview]
Message-ID: <20190619132231.6cr245e43utupl5j@localhost> (raw)
In-Reply-To: <3004130.oi6ZuZy1Zf@phil>
On Tue, Jun 11, 2019 at 10:53:57AM +0200, Heiko Stuebner wrote:
> Hi Arnd, Kevin, Olof,
>
> please find below and in the replies round1 of Rockchip updates for armsoc.
>
> As the tag implies this includes a lot of attention to the older rk3288-
> based Veyron line of ChromeOS devices.
>
> Please pull.
>
> Thanks
> Heiko
>
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.3-rockchip-dts32-1
>
> for you to fetch changes up to b8925b7c2f867df6ce3e20deb4b3e2b9b32b20ff:
>
> ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices (2019-06-06 12:41:04 +0200)
Merged, thanks!
-Olof
prev parent reply other threads:[~2019-06-19 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 8:53 [GIT PULL 1/3] Rockchip dts32 updates for 5.3 round 1 Heiko Stuebner
2019-06-11 8:54 ` [GIT PULL 2/3] Rockchip dts64 " Heiko Stuebner
2019-06-19 13:22 ` Olof Johansson
2019-06-11 8:55 ` [GIT PULL 3/3] Rockchip soc32 " Heiko Stuebner
2019-06-17 12:14 ` Olof Johansson
2019-06-19 13:22 ` 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=20190619132231.6cr245e43utupl5j@localhost \
--to=olof-nzht3qvonbneowh0uzbu5w@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).