From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] arm64: tegra: Device tree changes for v4.11-rc1
Date: Mon, 30 Jan 2017 07:54:21 +0100 [thread overview]
Message-ID: <20170130065421.GC3585@ulmo.ba.sec> (raw)
In-Reply-To: <20170130050017.GH18943@localhost>
On Sun, Jan 29, 2017 at 09:00:17PM -0800, Olof Johansson wrote:
> On Fri, Jan 27, 2017 at 10:21:21AM +0100, Thierry Reding wrote:
> > Hi ARM SoC maintainers,
> >
> > The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
> >
> > Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.11-arm64-dt
> >
> > for you to fetch changes up to 7bcf266462da736ae4b42d5c73cd5dc0da540772:
> >
> > arm64: tegra: Use symbolic reset identifiers (2017-01-27 10:13:24 +0100)
> >
> > Thanks,
> > Thierry
> >
> > ----------------------------------------------------------------
> > arm64: tegra: Device tree changes for v4.11-rc1
> >
> > This contains three patches that reintroduce symbolic identifiers for
> > clocks, resets and mailboxes. These had been converted to literals in
> > the v4.10 release to avoid complicated dependencies between branches.
> >
> > ----------------------------------------------------------------
> > Thierry Reding (3):
> > arm64: tegra: Use symbolic HSP identifiers
> > arm64: tegra: Use symbolic clock identifiers
> > arm64: tegra: Use symbolic reset identifiers
> >
> > arch/arm64/boot/dts/nvidia/tegra186.dtsi | 86 +++++++++++++++++---------------
> > 1 file changed, 45 insertions(+), 41 deletions(-)
>
> Merged, thanks!
>
> No more t186 material than this for 4.11, though? :(
Unfortunately not. After the holidays I was preoccupied with some
regressions and Tegra186 didn't see the amount of progress I had hoped.
There's more planned for v4.12, though.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170130/fabb43bb/attachment.sig>
next prev parent reply other threads:[~2017-01-30 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 9:21 [GIT PULL 1/4] memory: tegra: Changes for v4.11-rc1 Thierry Reding
2017-01-27 9:21 ` [GIT PULL 2/4] ARM: tegra: Core SoC changes " Thierry Reding
2017-01-30 4:58 ` Olof Johansson
2017-01-27 9:21 ` [GIT PULL 3/4] ARM: tegra: Device tree " Thierry Reding
2017-01-30 4:59 ` Olof Johansson
2017-01-27 9:21 ` [GIT PULL 4/4] arm64: " Thierry Reding
2017-01-30 5:00 ` Olof Johansson
2017-01-30 6:54 ` Thierry Reding [this message]
2017-01-30 4:58 ` [GIT PULL 1/4] memory: tegra: Changes " 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=20170130065421.GC3585@ulmo.ba.sec \
--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).