From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/3] ARM: dts: meson: fix UART device-tree schema validation
Date: Mon, 27 Dec 2021 19:00:23 +0100 [thread overview]
Message-ID: <20211227180026.4068352-1-martin.blumenstingl@googlemail.com> (raw)
Hello,
here are three UART device-tree schema related fixes for the 32-bit
ARM SoCs.
These patches don't fix any functionality which is why linux-stable
is not Cc'ed on them.
Martin Blumenstingl (3):
ARM: dts: meson: Fix the UART compatible strings
ARM: dts: meson8: Fix the UART device-tree schema validation
ARM: dts: meson8b: Fix the UART device-tree schema validation
arch/arm/boot/dts/meson.dtsi | 8 ++++----
arch/arm/boot/dts/meson8.dtsi | 24 ++++++++++++------------
arch/arm/boot/dts/meson8b.dtsi | 24 ++++++++++++------------
3 files changed, 28 insertions(+), 28 deletions(-)
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-12-27 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 18:00 Martin Blumenstingl [this message]
2021-12-27 18:00 ` [PATCH 1/3] ARM: dts: meson: Fix the UART compatible strings Martin Blumenstingl
2023-04-05 13:29 ` Ricardo Cañuelo
2023-04-05 17:14 ` Thorsten Leemhuis
2023-04-06 8:27 ` Ricardo Cañuelo
2023-04-06 9:06 ` Thorsten Leemhuis
2023-04-06 9:14 ` Greg KH
2023-04-10 6:09 ` Ricardo Cañuelo
2023-04-11 16:53 ` Linux regression tracking (Thorsten Leemhuis)
2021-12-27 18:00 ` [PATCH 2/3] ARM: dts: meson8: Fix the UART device-tree schema validation Martin Blumenstingl
2021-12-27 18:00 ` [PATCH 3/3] ARM: dts: meson8b: " Martin Blumenstingl
2021-12-31 15:38 ` [PATCH 0/3] ARM: dts: meson: fix " Martin Blumenstingl
2022-01-03 14:43 ` Neil Armstrong
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=20211227180026.4068352-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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