public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip arm64 devicetree fix for 4.20
Date: Wed, 12 Dec 2018 09:28:34 +0100	[thread overview]
Message-ID: <5618815.AsiCPEelux@phil> (raw)

Hi Arnd, Kevin, Olof,

one more fix for some regulators on the rk3399 rockpro64
turned up that may be nice to have in 4.20 still.

Please pull
Heiko

The following changes since commit c1d91f86a1b4c9c05854d59c6a0abd5d0f75b849:

  arm64: dts: rockchip: Fix PCIe reset polarity for rk3399-puma-haikou. (2018-11-13 15:02:07 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.20-rockchip-dts64fixes-2

for you to fetch changes up to 690e16bada6029694740d5501025faf483d14339:

  arm64: dts: rockchip: fix rk3399-rockpro64 regulator gpios (2018-12-06 13:46:16 +0100)

----------------------------------------------------------------
rockpro64 regulator fixes that cause stability issues

----------------------------------------------------------------
Oskari Lemmela (1):
      arm64: dts: rockchip: fix rk3399-rockpro64 regulator gpios

 arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2018-12-12  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  8:28 Heiko Stuebner [this message]
2018-12-12 22:21 ` [GIT PULL] Rockchip arm64 devicetree fix for 4.20 Olof Johansson

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=5618815.AsiCPEelux@phil \
    --to=heiko@sntech.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@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