public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/8] ARM: tegra: Device tree changes for v6.2-rc1
Date: Sat, 19 Nov 2022 02:20:23 +0100	[thread overview]
Message-ID: <20221119012025.3968358-6-thierry.reding@gmail.com> (raw)
In-Reply-To: <20221119012025.3968358-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.2-arm-dt

for you to fetch changes up to e4185804e191bdaeb10ebe00b1b4aa9e2f147a56:

  ARM: tegra: Remove duplicate pin entry in pinmux (2022-11-18 00:22:02 +0100)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Device tree changes for v6.2-rc1

This fixes various minor issues in device trees that are flagged by the
DT validation tools.

----------------------------------------------------------------
Thierry Reding (6):
      ARM: tegra: Use correct compatible string for ASUS TF101 panel
      ARM: tegra: Fixup pinmux node names
      ARM: tegra: Add missing power-supply for panels
      ARM: tegra: Fix nvidia,io-reset properties
      ARM: tegra: Remove unused interrupt-parent properties
      ARM: tegra: Remove duplicate pin entry in pinmux

 arch/arm/boot/dts/tegra114-asus-tf701t.dts         | 24 +++++++++++-----------
 arch/arm/boot/dts/tegra124-nyan-big.dts            |  3 ++-
 arch/arm/boot/dts/tegra124-nyan-blaze.dts          |  3 ++-
 arch/arm/boot/dts/tegra124-venice2.dts             |  3 ++-
 arch/arm/boot/dts/tegra20-acer-a500-picasso.dts    |  6 +++---
 arch/arm/boot/dts/tegra20-asus-tf101.dts           |  8 ++++----
 arch/arm/boot/dts/tegra20-seaboard.dts             |  6 +++---
 arch/arm/boot/dts/tegra20-tamonten.dtsi            |  6 +++---
 arch/arm/boot/dts/tegra20-ventana.dts              |  6 +++---
 .../boot/dts/tegra30-asus-transformer-common.dtsi  | 10 ++++-----
 arch/arm/boot/dts/tegra30-pegatron-chagall.dts     | 11 ++++------
 11 files changed, 42 insertions(+), 44 deletions(-)

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

  parent reply	other threads:[~2022-11-19  1:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:20 [GIT PULL 1/8] soc/tegra: Changes for v6.2-rc1 Thierry Reding
2022-11-19  1:20 ` [GIT PULL 2/8] firmware: tegra: " Thierry Reding
2022-11-19  1:20 ` [GIT PULL 3/8] clk: " Thierry Reding
2022-11-19  1:20 ` [GIT PULL 4/8] dt-bindings: " Thierry Reding
2022-11-21 12:10   ` Thierry Reding
2022-11-19  1:20 ` [GIT PULL 5/8] memory: tegra: " Thierry Reding
2022-11-19  1:20 ` Thierry Reding [this message]
2022-11-19  1:20 ` [GIT PULL 7/8] arm64: tegra: Device tree changes " Thierry Reding
2022-11-19  1:20 ` [GIT PULL 8/8] arm64: tegra: Default configuration updates " Thierry Reding

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=20221119012025.3968358-6-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.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