From: Geert Uytterhoeven <geert+renesas@glider.be>
To: David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>,
"David S . Miller" <davem@davemloft.net>,
Chanho Min <chanho.min@lge.com>
Cc: devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Neil Armstrong <narmstrong@baylibre.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/4] DT: Fix spelling of standard properties
Date: Fri, 6 Jul 2018 10:32:45 +0200 [thread overview]
Message-ID: <20180706083249.25399-1-geert+renesas@glider.be> (raw)
Hi all,
This patch series fixes misspellings of various standard DT properties
in DT binding documentation, DTS files, and examples.
While most of these are harmless, some of them may cause hard-to-debug
failures.
Changes compared to v5:
- Add Acked-by.
Changes compared to v4:
- Drop patches that have been applied already,
- Add Acked-by.
Changes compared to v3:
- Drop patches that have been applied already,
- Add Acked-by,
- Add new patches 5 and 6.
Changes compared to v2:
- Drop patches that have been applied already,
- Add Rob Herring's Acked-by,
- Add new patch "[PATCH v2 3/6] arm64: dts: lg1313: DT fix
s/#interrupts-cells/#interrupt-cells/".
Thanks for applying!
Geert Uytterhoeven (4):
arm64: dts: lg1312: DT fix s/#interrupts-cells/#interrupt-cells/
arm64: dts: lg1313: DT fix s/#interrupts-cells/#interrupt-cells/
dt-bindings: display: amlogic: DT fix s/resets-names/reset-names/
dt-bindings: net: btusb: DT fix s/interrupt-name/interrupt-names/
.../devicetree/bindings/display/amlogic,meson-dw-hdmi.txt | 2 +-
Documentation/devicetree/bindings/net/btusb.txt | 2 +-
arch/arm64/boot/dts/lg/lg1312.dtsi | 2 +-
arch/arm64/boot/dts/lg/lg1313.dtsi | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2018-07-06 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:32 Geert Uytterhoeven [this message]
2018-07-06 8:32 ` [PATCH v5 1/4] arm64: dts: lg1312: DT fix s/#interrupts-cells/#interrupt-cells/ Geert Uytterhoeven
2018-07-06 8:32 ` [PATCH v5 2/4] arm64: dts: lg1313: " Geert Uytterhoeven
2018-07-06 8:32 ` [PATCH v5 3/4] dt-bindings: display: amlogic: DT fix s/resets-names/reset-names/ Geert Uytterhoeven
2018-07-06 8:32 ` [PATCH v5 4/4] dt-bindings: net: btusb: DT fix s/interrupt-name/interrupt-names/ Geert Uytterhoeven
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=20180706083249.25399-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=airlied@linux.ie \
--cc=carlo@caione.org \
--cc=chanho.min@lge.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=netdev@vger.kernel.org \
--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