From: Rob Herring <robh@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Duc Dang <dhdang@apm.com>, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-kernel@vger.kernel.org, Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH 2 1/2] arm64: dts: apm: Use lowercase consistently for hex constants
Date: Thu, 16 Jun 2016 17:28:29 -0500 [thread overview]
Message-ID: <20160616222829.GA25357@rob-hp-laptop> (raw)
In-Reply-To: <20160614130020.22169.51495.stgit@bhelgaas-glaptop2.roam.corp.google.com>
On Tue, Jun 14, 2016 at 08:00:20AM -0500, Bjorn Helgaas wrote:
> The convention in these files is to use lowercase for "0x" prefixes and for
> the hex constants themselves, but a few changes didn't follow that
> convention, which makes the file annoying to read.
>
> Use lowercase consistently for the hex constants. No functional change
> intended.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> .../devicetree/bindings/net/apm-xgene-enet.txt | 4 +-
> arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 40 ++++++++++----------
> arch/arm64/boot/dts/apm/apm-storm.dtsi | 36 +++++++++---------
> 3 files changed, 40 insertions(+), 40 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-06-16 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 13:00 [PATCH 2 0/2] arm64: Trivial DT cleanups Bjorn Helgaas
2016-06-14 13:00 ` [PATCH 2 1/2] arm64: dts: apm: Use lowercase consistently for hex constants Bjorn Helgaas
2016-06-16 22:28 ` Rob Herring [this message]
2016-06-17 3:06 ` Duc Dang
2016-06-14 13:00 ` [PATCH 2 2/2] arm64: dts: apm: Remove leading '0x' from unit addresses Bjorn Helgaas
[not found] ` <20160614130030.22169.93519.stgit-1RhO1Y9PlrlHTL0Zs8A6p/gx64E7kk8eUsxypvmhUTTZJqsBc5GL+g@public.gmane.org>
2016-06-16 22:29 ` Rob Herring
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=20160616222829.GA25357@rob-hp-laptop \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dhdang@apm.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
/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