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 4/5] ARM: tegra: Devicetree changes for v4.5-rc1
Date: Wed, 30 Dec 2015 16:48:28 +0100	[thread overview]
Message-ID: <20151230154828.GC7085@ulmo> (raw)
In-Reply-To: <20151222195520.GI30172@localhost>

On Tue, Dec 22, 2015 at 11:55:20AM -0800, Olof Johansson wrote:
> On Thu, Dec 17, 2015 at 01:50:38PM +0100, Thierry Reding wrote:
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> > 
> >   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.5-dt
> > 
> > for you to fetch changes up to 336f79c7b6d7d04f7dad0361b9f4c8995107c062:
> > 
> >   arm64: tegra: Add NVIDIA Jetson TX1 Developer Kit support (2015-11-24 16:52:25 +0100)
> > 
> > Note that this pulls in the device tree bindings for the Tegra210 clock
> > and reset controller. A separate pull request is sent to the clock tree
> > maintainers including this commit. I've included this patch in the diff
> > stat below.
> > 
> > Thanks,
> > Thierry
> > 
> > ----------------------------------------------------------------
> > ARM: tegra: Devicetree changes for v4.5-rc1
> > 
> > This adds support for the Tegra132 Norrin and various Tegra210-based
> > reference designs. There is also an initial device tree for the Jetson
> > TX1 development kit.
> 
> Unfortunately can't merge this due to the feedback on your soc branch that is
> part of this.

In the past we've sent devicetree updates via a single branch for both
32-bit and 64-bit ARM. That's not the case for this cycle, but if we had
changes to both 32-bit and 64-bit ARM device trees, would you prefer
separate branches for those as well?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151230/b1b15554/attachment.sig>

  reply	other threads:[~2015-12-30 15:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:50 [GIT PULL 1/5] clk: tegra: Changes for v4.5-rc1 Thierry Reding
2015-12-17 12:50 ` [GIT PULL 2/5] memory: " Thierry Reding
2015-12-22 19:53   ` Olof Johansson
2015-12-30 15:36     ` Thierry Reding
2015-12-17 12:50 ` [GIT PULL 3/5] ARM: tegra: Core SoC changes " Thierry Reding
2015-12-22 19:54   ` Olof Johansson
2015-12-30 15:46     ` Thierry Reding
2016-01-12 18:09       ` Olof Johansson
2016-01-12 18:11   ` Olof Johansson
2015-12-17 12:50 ` [GIT PULL 4/5] ARM: tegra: Devicetree " Thierry Reding
2015-12-22 19:55   ` Olof Johansson
2015-12-30 15:48     ` Thierry Reding [this message]
2016-01-12 18:11       ` Olof Johansson
2015-12-17 12:50 ` [GIT PULL 5/5] ARM: tegra: Default configuration updates " Thierry Reding
2015-12-22 19:56   ` Olof Johansson
2016-01-05  0:23 ` [GIT PULL 1/5] clk: tegra: Changes " Michael Turquette

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=20151230154828.GC7085@ulmo \
    --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).