From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-spi@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-iio@vger.kernel.org,
linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
linux-media@vger.kernel.org, alsa-devel@alsa-project.org,
linux-mmc@vger.kernel.org, linux-mtd@lists.infradead.org,
netdev@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: Whitespace clean-ups in schema files
Date: Wed, 12 Aug 2020 15:32:32 -0700 [thread overview]
Message-ID: <f5dedf2d8d8057de3eaa2f9126f44cebb0653b09.camel@perches.com> (raw)
In-Reply-To: <20200812203618.2656699-1-robh@kernel.org>
On Wed, 2020-08-12 at 14:36 -0600, Rob Herring wrote:
> Clean-up incorrect indentation, extra spaces, long lines, and missing
> EOF newline in schema files. Most of the clean-ups are for list
> indentation which should always be 2 spaces more than the preceding
^
> keyword.
[]
> diff --git a/Documentation/devicetree/bindings/arm/arm,integrator.yaml b/Documentation/devicetree/bindings/arm/arm,integrator.yaml
> index 192ded470e32..f0daf990e077 100644
> --- a/Documentation/devicetree/bindings/arm/arm,integrator.yaml
> +++ b/Documentation/devicetree/bindings/arm/arm,integrator.yaml
> @@ -67,9 +67,9 @@ patternProperties:
> compatible:
> items:
> - enum:
> - - arm,integrator-ap-syscon
> - - arm,integrator-cp-syscon
> - - arm,integrator-sp-syscon
> + - arm,integrator-ap-syscon
> + - arm,integrator-cp-syscon
> + - arm,integrator-sp-syscon
Confused a bit here.
- enum:
10 spaces to dash
old line:
- arm,integrator-ap-syscon
12 spaces to dash
new line:
- arm,integrator-ap-syscon
14 spaces to dash
Is it supposed to be 2 spaces more than the preceding line
or 4 more?
next prev parent reply other threads:[~2020-08-12 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 20:36 [PATCH] dt-bindings: Whitespace clean-ups in schema files Rob Herring
2020-08-12 21:34 ` Sam Ravnborg
2020-08-12 22:41 ` Rob Herring
2020-08-16 8:44 ` Jonathan Cameron
2020-08-12 22:32 ` Joe Perches [this message]
2020-08-12 23:05 ` Rob Herring
2020-08-13 7:50 ` Geert Uytterhoeven
2020-08-13 10:31 ` Luca Ceresoli
2020-08-14 14:51 ` Rob Herring
2020-08-14 16:30 ` Luca Ceresoli
2020-08-25 7:10 ` Wolfram Sang
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=f5dedf2d8d8057de3eaa2f9126f44cebb0653b09.camel@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).