From: Thierry Reding <thierry.reding@gmail.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, gnurou@gmail.com
Subject: Re: [PATCH v2] dt-bindings: Add documentation for GP10B GPU
Date: Tue, 4 Apr 2017 15:21:57 +0200 [thread overview]
Message-ID: <20170404132157.GA843@ulmo.ba.sec> (raw)
In-Reply-To: <20170330092644.11890-1-acourbot@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
On Thu, Mar 30, 2017 at 06:26:44PM +0900, Alexandre Courbot wrote:
> GP10B's definition is mostly similar to GK20A's and GM20B's. The only
> noticeable difference is the use of power domains instead of a regulator
> for power supply.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> Changes since v1:
> - It's much better when it compiles.
>
> .../devicetree/bindings/gpu/nvidia,gk20a.txt | 25 +++++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
Applied to for-4.12/arm64/dt, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-04 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:18 [PATCH 1/2] dt-bindings: Add documentation for GP10B GPU Alexandre Courbot
2017-03-30 9:18 ` [PATCH 2/2] arm64: tegra: Add GPU node for Tegra 186 Alexandre Courbot
2017-03-30 9:26 ` [PATCH v2] dt-bindings: Add documentation for GP10B GPU Alexandre Courbot
2017-03-31 12:56 ` Thierry Reding
2017-04-08 10:20 ` Alexandre Courbot
2017-04-03 15:55 ` Rob Herring
2017-04-04 13:21 ` Thierry Reding [this message]
2017-03-30 9:28 ` [PATCH v2] arm64: tegra: Add GPU node for Tegra 186 Alexandre Courbot
2017-04-04 13:22 ` Thierry Reding
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=20170404132157.GA843@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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