[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <176831872457.153367.14622745892314897122.b4-ty@kernel.org>
Date: Tue, 13 Jan 2026 15:38:44 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-mediatek@...ts.infradead.org,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
sen.chu@...iatek.com, sean.wang@...iatek.com, macpaul.lin@...iatek.com,
lee@...nel.org, matthias.bgg@...il.com, lgirdwood@...il.com,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kernel@...labora.com
Subject: Re: (subset) [PATCH 0/6] Fix dtbs_check warnings for MediaTek
Helio X10 platform
On Tue, 13 Jan 2026 11:59:54 +0100, AngeloGioacchino Del Regno wrote:
> This series fixes various dtbs_check warnings happening on the MediaTek
> Helio X10 platform devicetrees.
>
> Depending on correctness, either the bindings or the devicetree was
> changed as a dtbs_check warning fix.
>
> AngeloGioacchino Del Regno (6):
> dt-bindings: mfd: mediatek,mt8195-scpsys: Add mediatek,mt6795-scpsys
> dt-bindings: mfd: mediatek: mt6397: Add missing MT6331 regulator
> compat
> dt-bindings: regulator: mediatek,mt6331: Add missing ldo-vio28 vreg
> arm64: dts: mediatek: mt6331: Fix VCAM IO regulator name
> arm64: dts: mediatek: mt6795: Fix issues in SCPSYS node
> arm64: dts: mediatek: mt6795-xperia-m5: Rename PMIC leds node
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[3/6] dt-bindings: regulator: mediatek,mt6331: Add missing ldo-vio28 vreg
commit: de9f1b1583aecb246b659effb03f2456604fab64
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists