From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] dt-bindings: Updates for v4.12-rc1
Date: Wed, 19 Apr 2017 06:10:36 -0700 [thread overview]
Message-ID: <20170419131036.GA29219@localhost> (raw)
In-Reply-To: <20170406231020.32048-1-thierry.reding@gmail.com>
On Fri, Apr 07, 2017 at 01:10:17AM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.12-dt-bindings
>
> for you to fetch changes up to bf594a896cdbae4a581eb80a2bdbda8df6997d75:
>
> dt-bindings: Add documentation for GP10B GPU (2017-04-04 16:08:18 +0200)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> dt-bindings: Updates for v4.12-rc1
>
> This contains an update for the flow controller device tree binding as
> well as the addition of the binding for the GP10B GPU found on the new
> Tegra186 (Parker) SoC.
Hm, usually we bundle bindings updates with the driver update that makes use of
the new/amended binding.
Anyway, merged this into next/dt. Thanks!
-Olof
prev parent reply other threads:[~2017-04-19 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 23:10 [GIT PULL 1/4] dt-bindings: Updates for v4.12-rc1 Thierry Reding
2017-04-06 23:10 ` [GIT PULL 2/4] ARM: tegra: Maintainer changes " Thierry Reding
2017-04-19 13:12 ` Olof Johansson
2017-04-06 23:10 ` [GIT PULL 3/4] soc/tegra: Core SoC " Thierry Reding
2017-04-19 13:17 ` Olof Johansson
2017-04-06 23:10 ` [GIT PULL 4/4] arm64: tegra: Device tree " Thierry Reding
2017-04-19 13:19 ` Olof Johansson
2017-04-19 15:24 ` Thierry Reding
2017-04-19 13:10 ` Olof Johansson [this message]
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=20170419131036.GA29219@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).