Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@linaro.org>
To: arm@kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-arm-msm@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Olof Johansson <olof@lixom.net>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Qualcomm Device Tree updates for 4.21
Date: Mon,  3 Dec 2018 13:39:04 -0600	[thread overview]
Message-ID: <1543865944-3591-4-git-send-email-andy.gross@linaro.org> (raw)
In-Reply-To: <1543865944-3591-1-git-send-email-andy.gross@linaro.org>

The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-dts-for-4.21

for you to fetch changes up to 972910948fb6f555e83f37bc6172f51984d738a9:

  ARM: dts: qcom: Remove Arrow SD600 eval board (2018-11-28 17:36:41 -0600)

----------------------------------------------------------------
Qualcomm Device Tree Changes for v4.21

* Add entry for Qualcomm TSENS thermal drivers
* Update msm8974 thermal entries
* Fix msm8974 Hammerhead magnetometer gpios
* Add SoC specific compatibles for SDHC nodes
* Remove Arrow SD600 eval board

----------------------------------------------------------------
Amit Kucheria (3):
      MAINTAINERS: Add entry for Qualcomm TSENS thermal drivers
      ARM: dts: msm8974: thermal: split address space into two
      ARM: dts: msm8974: thermal: Add "qcom,sensors" property

Andy Gross (1):
      ARM: dts: qcom: Remove Arrow SD600 eval board

Brian Masney (1):
      ARM: dts: qcom: msm8974-hammerhead: correct gpios property on magnetometer

Douglas Anderson (1):
      ARM: dts: qcom: Add SoC-specific string for sdhci-msm-v4 nodes

 MAINTAINERS                                        |   7 +
 arch/arm/boot/dts/Makefile                         |   1 -
 .../dts/qcom-apq8064-arrow-sd-600eval-pins.dtsi    |  53 ---
 .../arm/boot/dts/qcom-apq8064-arrow-sd-600eval.dts | 415 ---------------------
 arch/arm/boot/dts/qcom-apq8084.dtsi                |   4 +-
 .../dts/qcom-msm8974-lge-nexus5-hammerhead.dts     |   3 +-
 arch/arm/boot/dts/qcom-msm8974.dtsi                |  12 +-
 7 files changed, 17 insertions(+), 478 deletions(-)
 delete mode 100644 arch/arm/boot/dts/qcom-apq8064-arrow-sd-600eval-pins.dtsi
 delete mode 100644 arch/arm/boot/dts/qcom-apq8064-arrow-sd-600eval.dts

  parent reply	other threads:[~2018-12-03 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 19:39 [GIT PULL] Qualcomm ARM64 Defconfig updates for 4.21 Andy Gross
2018-12-03 19:39 ` [GIT PULL] Qualcomm ARM64 DT " Andy Gross
2018-12-03 21:04   ` Olof Johansson
2018-12-03 19:39 ` [GIT PULL] Qualcomm Driver " Andy Gross
2018-12-03 21:11   ` Olof Johansson
2018-12-03 19:39 ` Andy Gross [this message]
2018-12-03 21:05   ` [GIT PULL] Qualcomm Device Tree " Olof Johansson
2018-12-03 21:03 ` [GIT PULL] Qualcomm ARM64 Defconfig " 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=1543865944-3591-4-git-send-email-andy.gross@linaro.org \
    --to=andy.gross@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olof@lixom.net \
    /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