linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/4] ARM: tegra: Device tree changes for v4.13-rc1
Date: Fri, 16 Jun 2017 10:13:05 +0200	[thread overview]
Message-ID: <20170616081306.11505-3-thierry.reding@gmail.com> (raw)
In-Reply-To: <20170616081306.11505-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:

  Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)

are available in the git repository at:

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

for you to fetch changes up to 508d690e94218d306ab2092d6ee95ca75f9fa98b:

  ARM: dts: tegra: fix PCI bus dtc warnings (2017-06-13 16:49:57 +0200)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Device tree changes for v4.13-rc1

This removes support for the Whistler board, which only a handful of
people ever had access to and which doesn't provide any features over
other Tegra20 devices that we support.

Also this cleans up some PCI related device tree content in preparation
for a future DTC release that has additional checks for the PCI bus.

----------------------------------------------------------------
Rob Herring (1):
      ARM: dts: tegra: fix PCI bus dtc warnings

Stephen Warren (1):
      ARM: tegra: remove Whistler support

 Documentation/devicetree/bindings/arm/tegra.txt |   1 -
 arch/arm/boot/dts/Makefile                      |   3 +-
 arch/arm/boot/dts/tegra124-apalis-eval.dts      |   2 +-
 arch/arm/boot/dts/tegra124-apalis.dtsi          |   2 +-
 arch/arm/boot/dts/tegra124-jetson-tk1.dts       |   2 +-
 arch/arm/boot/dts/tegra124.dtsi                 |   4 +-
 arch/arm/boot/dts/tegra20-harmony.dts           |   2 +-
 arch/arm/boot/dts/tegra20-tamonten.dtsi         |   2 +-
 arch/arm/boot/dts/tegra20-tec.dts               |   2 +-
 arch/arm/boot/dts/tegra20-trimslice.dts         |   2 +-
 arch/arm/boot/dts/tegra20-whistler.dts          | 636 ------------------------
 arch/arm/boot/dts/tegra20.dtsi                  |   4 +-
 arch/arm/boot/dts/tegra30-apalis-eval.dts       |   2 +-
 arch/arm/boot/dts/tegra30-apalis.dtsi           |   2 +-
 arch/arm/boot/dts/tegra30-beaver.dts            |   2 +-
 arch/arm/boot/dts/tegra30-cardhu.dtsi           |   2 +-
 arch/arm/boot/dts/tegra30.dtsi                  |   5 +-
 17 files changed, 22 insertions(+), 653 deletions(-)
 delete mode 100644 arch/arm/boot/dts/tegra20-whistler.dts

  parent reply	other threads:[~2017-06-16  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  8:13 [GIT PULL 1/4] soc/tegra: Changes for v4.13-rc1 Thierry Reding
2017-06-16  8:13 ` [GIT PULL 2/4] firmware: tegra: " Thierry Reding
2017-06-19  4:01   ` Olof Johansson
2017-06-16  8:13 ` Thierry Reding [this message]
2017-06-19  4:01   ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Olof Johansson
2017-06-16  8:13 ` [GIT PULL 4/4] arm64: " Thierry Reding
2017-06-19  4:02   ` Olof Johansson
2017-06-19  4:00 ` [GIT PULL 1/4] soc/tegra: Changes " Olof Johansson
2017-06-19  5:59   ` Mikko Perttunen
2017-06-19  6:04     ` 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=20170616081306.11505-3-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --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).