From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
nfraprado@collabora.com
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 3/4] arm64: dts: mediatek: Remove mt6589 wdt fallback string from mt8195
Date: Wed, 20 Jul 2022 15:11:54 +0200 [thread overview]
Message-ID: <bfefe80e-9f14-fccc-bd4a-58ddadfc287f@collabora.com> (raw)
In-Reply-To: <20220720125015.13797-4-allen-kh.cheng@mediatek.com>
Il 20/07/22 14:50, Allen-KH Cheng ha scritto:
> The watchdog driver for mt8195 relies on DT data. The fallback
> compatible "mediatek,mt6589-wdt" won't work.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2022-07-20 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 12:50 [PATCH v3 0/4] mediatek: watchdog: Fix compatible fallbacks Allen-KH Cheng
2022-07-20 12:50 ` [PATCH v3 1/4] dt-binding: mediatek: watchdog: Fix compatible fallbacks and example Allen-KH Cheng
2022-07-20 13:10 ` AngeloGioacchino Del Regno
2022-07-25 22:27 ` Rob Herring
2022-07-20 12:50 ` [PATCH v3 2/4] arm64: dts: mediatek: Remove mt6589 wdt fallback string from mt7986 Allen-KH Cheng
2022-07-20 13:11 ` AngeloGioacchino Del Regno
2022-07-20 12:50 ` [PATCH v3 3/4] arm64: dts: mediatek: Remove mt6589 wdt fallback string from mt8195 Allen-KH Cheng
2022-07-20 13:11 ` AngeloGioacchino Del Regno [this message]
2022-07-20 12:50 ` [PATCH v3 4/4] arm64: dts: mediatek: Fix the watchdog node name Allen-KH Cheng
2022-07-20 13:12 ` 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=bfefe80e-9f14-fccc-bd4a-58ddadfc287f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®