linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Rockchip dts64 fixes for 4.16
Date: Thu, 22 Feb 2018 17:47:48 +0100	[thread overview]
Message-ID: <CAK8P3a2QXnUCaj1vDa6PePWWJAcyvMe-fRAhVqLd3QdFKEWRLg@mail.gmail.com> (raw)
In-Reply-To: <1708943.A4pxJccnVY@phil>

On Sun, Feb 18, 2018 at 4:41 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
>   Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.16-rockchip-dts64fixes-1
>
> for you to fetch changes up to ca9eee95a2decc6f60bed65b5b836a26bff825c1:
>
>   arm64: dts: rockchip: Fix DWMMC clocks (2018-02-16 10:30:25 +0100)
>
> ----------------------------------------------------------------
> Fixes of dwmmc tuning clocks that may make probing HS cards fail,
> adding the grf-vio clock to the edp so that it can also be build
> as module, correct pcie ep-gpio on the sapphire board and finally
> a fix that makes the gmac work at gigabit speeds on the rk3328-rock64.

Pulled into fixes, thanks!

     Arnd

  reply	other threads:[~2018-02-22 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 15:40 [GIT PULL 1/2] Rockchip dts32 fixes for 4.16 Heiko Stuebner
2018-02-18 15:41 ` [GIT PULL 2/2] Rockchip dts64 " Heiko Stuebner
2018-02-22 16:47   ` Arnd Bergmann [this message]
2018-02-22 16:47 ` [GIT PULL 1/2] Rockchip dts32 " Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2018-03-12  8:37 Heiko Stuebner
2018-03-12  8:38 ` [GIT PULL 2/2] Rockchip dts64 " Heiko Stuebner
2018-03-12 14:35   ` Arnd Bergmann

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=CAK8P3a2QXnUCaj1vDa6PePWWJAcyvMe-fRAhVqLd3QdFKEWRLg@mail.gmail.com \
    --to=arnd@arndb.de \
    --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).