public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Bresticker <abrestic@chromium.org>
Subject: Re: [PATCH v2] arm64: tegra: Add pinmux for Smaug board
Date: Tue, 12 Apr 2016 17:16:31 +0200	[thread overview]
Message-ID: <20160412151631.GD25160@ulmo.ba.sec> (raw)
In-Reply-To: <1460411582-7435-1-git-send-email-rklein@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

On Mon, Apr 11, 2016 at 05:53:02PM -0400, Rhyland Klein wrote:
> Add pinmux node for Tegra210 Smaug board.
> 
> Signed-off-by: Rhyland Klein <rklein@nvidia.com>
> ---
> v2:
>  - Fixed address to align with recent patch:
>    'arm64: tegra: Remove 0, prefix from unit-addresses'
> 
>  arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 1271 +++++++++++++++++++++++++
>  1 file changed, 1271 insertions(+)

This didn't apply cleanly because, while it was updated to not add a 0,
prefix to the unit-address itself, it wasn't based on top of the patch
that removed the 0, prefix from the serial@0,70006000 node below it.

No biggie, just bringing it up to let you know that you don't usually
need to bother about these details, I could've just as easily fixed up
your first version when applying.

For the record, applied now.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-04-12 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 21:53 [PATCH v2] arm64: tegra: Add pinmux for Smaug board Rhyland Klein
2016-04-12 15:16 ` Thierry Reding [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=20160412151631.GD25160@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=abrestic@chromium.org \
    --cc=gnurou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rklein@nvidia.com \
    --cc=swarren@wwwdotorg.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