From: Chen-Yu Tsai <wenst@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH 0/3] arm64: dts: mediatek: Random DT cleanups
Date: Thu, 30 Nov 2023 15:40:28 +0800 [thread overview]
Message-ID: <20231130074032.913511-1-wenst@chromium.org> (raw)
Hi,
Here are some random DT cleanups that I've accumulated. This should get
rid of some warnings.
Please have a look.
ChenYu
Chen-Yu Tsai (3):
arm64: dts: mt8183: kukui-jacuzzi: Drop bogus anx7625 panel_flag
property
arm64: dts: mt6358: Drop bogus "regulator-fixed" compatible properties
arm64: dts: mediatek: mt8186: Fix alias prefix for ovl_2l0
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 13 -------------
.../boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi | 1 -
arch/arm64/boot/dts/mediatek/mt8186.dtsi | 2 +-
3 files changed, 1 insertion(+), 15 deletions(-)
--
2.43.0.rc2.451.g8631bc7472-goog
next reply other threads:[~2023-11-30 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 7:40 Chen-Yu Tsai [this message]
2023-11-30 7:40 ` [PATCH 1/3] arm64: dts: mt8183: kukui-jacuzzi: Drop bogus anx7625 panel_flag property Chen-Yu Tsai
2023-12-01 9:04 ` AngeloGioacchino Del Regno
2023-11-30 7:40 ` [PATCH 2/3] arm64: dts: mt6358: Drop bogus "regulator-fixed" compatible properties Chen-Yu Tsai
2023-12-01 9:03 ` AngeloGioacchino Del Regno
2023-11-30 7:40 ` [PATCH 3/3] arm64: dts: mediatek: mt8186: Fix alias prefix for ovl_2l0 Chen-Yu Tsai
2023-12-01 9:04 ` AngeloGioacchino Del Regno
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=20231130074032.913511-1-wenst@chromium.org \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).