From: patchwork-bot+linux-soc@kernel.org
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: soc@kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8195: Fix vdosys* compatible strings
Date: Fri, 03 Feb 2023 14:20:29 +0000 [thread overview]
Message-ID: <167543402960.11069.3454802065941836878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202104014.2931517-1-wenst@chromium.org>
Hello:
This patch was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 2 Feb 2023 18:40:14 +0800 you wrote:
> When vdosys1 was initially added, it was incorrectly assumed to be
> compatible with vdosys0, and thus both had the same mt8195-mmsys
> compatible attached.
>
> This has since been corrected in commit b237efd47df7 ("dt-bindings:
> arm: mediatek: mmsys: change compatible for MT8195") and commit
> 82219cfbef18 ("dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible
> for MT8195"). The device tree needs to be fixed as well, otherwise
> the vdosys1 block fails to work, and causes its dependent power domain
> controller to not work either.
>
> [...]
Here is the summary with links:
- arm64: dts: mediatek: mt8195: Fix vdosys* compatible strings
https://git.kernel.org/soc/soc/c/97801cfcf956
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-03 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 10:40 [PATCH] arm64: dts: mediatek: mt8195: Fix vdosys* compatible strings Chen-Yu Tsai
2023-02-02 10:40 ` Chen-Yu Tsai
2023-02-02 11:42 ` AngeloGioacchino Del Regno
2023-02-02 11:42 ` AngeloGioacchino Del Regno
2023-02-02 11:52 ` Matthias Brugger
2023-02-02 11:52 ` Matthias Brugger
2023-02-03 14:20 ` patchwork-bot+linux-soc [this message]
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=167543402960.11069.3454802065941836878.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=wenst@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.