public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip dts32 changes for 5.20 #1
Date: Tue, 05 Jul 2022 13:11:23 +0200	[thread overview]
Message-ID: <14795241.VsHLxoZxqI@phil> (raw)

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.20-rockchip-dts32-1

for you to fetch changes up to e5a3cbe8b45b0a436a39cc969b7bcc8353248018:

  ARM: dts: rockchip: correct gpio-keys properties on rk3288-tinker (2022-06-22 21:04:38 +0200)

----------------------------------------------------------------
NFC flash node on rk3066a-mk808 and some dts styling fixes
(alignment and node names).

----------------------------------------------------------------
Johan Jonker (1):
      ARM: dts: rockchip: enable nfc node in rk3066a-mk808.dts

Krzysztof Kozlowski (3):
      ARM: dts: rockchip: adjust whitespace around '='
      ARM: dts: rockchip: align gpio-key node names with dtschema
      ARM: dts: rockchip: correct gpio-keys properties on rk3288-tinker

 arch/arm/boot/dts/rk3066a-bqcurie2.dts                 |  4 ++--
 arch/arm/boot/dts/rk3066a-mk808.dts                    | 18 ++++++++++++++++++
 arch/arm/boot/dts/rk3066a-rayeager.dts                 |  2 +-
 arch/arm/boot/dts/rk3188-bqedison2qc.dts               |  4 ++--
 arch/arm/boot/dts/rk3188-px3-evb.dts                   |  2 +-
 arch/arm/boot/dts/rk3188-radxarock.dts                 |  2 +-
 arch/arm/boot/dts/rk3229-evb.dts                       |  2 +-
 arch/arm/boot/dts/rk3288-evb.dtsi                      |  2 +-
 arch/arm/boot/dts/rk3288-firefly-reload.dts            |  2 +-
 arch/arm/boot/dts/rk3288-firefly.dtsi                  |  2 +-
 arch/arm/boot/dts/rk3288-phycore-rdk.dts               |  4 ++--
 arch/arm/boot/dts/rk3288-popmetal.dts                  |  2 +-
 arch/arm/boot/dts/rk3288-r89.dts                       |  2 +-
 arch/arm/boot/dts/rk3288-rock2-square.dts              |  2 +-
 arch/arm/boot/dts/rk3288-tinker.dtsi                   |  4 +---
 .../arm/boot/dts/rk3288-veyron-broadcom-bluetooth.dtsi | 10 +++++-----
 arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi        |  2 +-
 arch/arm/boot/dts/rk3288-veyron-minnie.dts             |  4 ++--
 arch/arm/boot/dts/rk3288-veyron-pinky.dts              |  2 +-
 arch/arm/boot/dts/rk3288-veyron.dtsi                   |  2 +-
 arch/arm/boot/dts/rv1108-elgin-r1.dts                  | 14 +++++++-------
 arch/arm/boot/dts/rv1108-evb.dts                       | 14 +++++++-------
 arch/arm/boot/dts/rv1108.dtsi                          |  2 +-
 23 files changed, 60 insertions(+), 44 deletions(-)




_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

                 reply	other threads:[~2022-07-05 11:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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