linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 7/10] ARM: tegra: Device tree changes for v4.10-rc1
Date: Fri, 18 Nov 2016 18:36:24 -0800	[thread overview]
Message-ID: <20161119023624.GR2543@localhost> (raw)
In-Reply-To: <20161118161719.24153-7-thierry.reding@gmail.com>

On Fri, Nov 18, 2016 at 05:17:16PM +0100, Thierry Reding wrote:
> Hi ARM SoC maintainers,
> 
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
> 
>   Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.10-arm-dt
> 
> for you to fetch changes up to 5e8a724d143308f3195375951b0c8f01b2ca59fe:
> 
>   ARM: tegra: apalis-tk1: Drop leading 0 from unit-address (2016-11-08 11:14:02 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> ARM: tegra: Device tree changes for v4.10-rc1
> 
> Adds support for GMI on Tegra20 and Tegra30 and enables the GPU on Nyan
> Chromebooks. It also enables sound support on various Toradex devices.

Merged, thanks!


-Olof

  reply	other threads:[~2016-11-19  2:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 16:17 [GIT PULL 1/10] mailbox: Add Tegra HSP driver Thierry Reding
2016-11-18 16:17 ` [GIT PULL 2/10] firmware: Add Tegra IVC and BPMP support Thierry Reding
2016-11-19  2:31   ` Olof Johansson
2016-11-21  8:29     ` Thierry Reding
2016-12-04  5:10       ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 3/10] reset: Add Tegra BPMP reset driver Thierry Reding
2016-11-19  2:32   ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 4/10] bus: Add Tegra GMI support Thierry Reding
2016-11-19  2:33   ` Olof Johansson
2016-11-19  2:35   ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 5/10] soc: tegra: Core SoC changes for v4.10-rc1 Thierry Reding
2016-11-19  2:35   ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 6/10] dt-bindings: Cleanups and additions " Thierry Reding
2016-11-19  2:35   ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 7/10] ARM: tegra: Device tree changes " Thierry Reding
2016-11-19  2:36   ` Olof Johansson [this message]
2016-11-18 16:17 ` [GIT PULL 8/10] ARM: tegra: Default configuration updates " Thierry Reding
2016-11-19  2:37   ` Olof Johansson
2016-11-18 16:17 ` [GIT PULL 9/10] arm64: tegra: Device tree changes " Thierry Reding
2016-11-19  2:40   ` Olof Johansson
2016-11-21  8:22     ` Thierry Reding
2016-12-04  5:13       ` Olof Johansson
2016-11-21 10:23   ` [GIT PULL v2 " Thierry Reding
2016-11-30 16:08     ` Arnd Bergmann
2016-11-18 16:17 ` [GIT PULL 10/10] arm64: tegra: Default configuration updates " Thierry Reding
2016-11-30 16:10   ` Arnd Bergmann
2016-11-30 16:39     ` Thierry Reding
2016-11-30 21:12       ` Arnd Bergmann
2016-11-19  2:27 ` [GIT PULL 1/10] mailbox: Add Tegra HSP driver Olof Johansson
2016-11-21  8:17   ` Thierry Reding
2016-12-04  5:25     ` 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=20161119023624.GR2543@localhost \
    --to=olof@lixom.net \
    --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).