On Mon, 27 Oct 2025 12:05:18 +0100, AngeloGioacchino Del Regno wrote:

Changes in v11:
 - Removed unnecessary #address-cells in all mt6316 bindings

Changes in v10:
 - Added "struct" prefix to structs kerneldoc
 - Renamed struct mtk_spmi_pmic_pdata to mtk_spmi_pmic_variant
 - Added "REG_" to MT6363/73 mfd register definitions to disambiguate
 - Expanded MTK_SPMI_PMIC_IRQ_GROUP macro parameter names as suggested
 - Some rewording of comments as suggested, addition of more comments
 - Refactored IRQ domain handling due to deprecation of function
   irq_domain_add_tree() to use the new irq_domain_create_tree()
 - Fixed to use generic_handle_domain_irq_safe() to avoid races
 - Added support for two interrupt cells in translation
 - Removed .irq_lock() and .irq_unlock() in favor of lockdep classes
 - Added support for handling PMICs without IRQ Group register for
   upcoming MT6685 implementation

[...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators
      commit: 40a7c5db9020079547358f486ef12d57c1a7aa1f
[2/9] regulator: Add support for MediaTek MT6316 SPMI PMIC Regulators
      commit: a87a7b3530728fb7477a74c27fc27e060bf5684f
[3/9] dt-bindings: regulator: Document MediaTek MT6363 PMIC Regulators
      commit: d0f9f5b7a3356b43f78b37b9cc3671ecc7469356
[4/9] regulator: Add support for MediaTek MT6363 SPMI PMIC Regulators
      commit: 3c36965df80801344850388592e95033eceea05b

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