On Thu, 28 Sep 2023 16:55:23 +0800, Chen-Yu Tsai wrote: > This is v4 of my MT6366 PMIC split-out-of-MT6358 cleanup series. The two > PMICs are mostly identical, except for the regulator bits. The MT6366 is > missing the VCAM* (camera related) LDOs, but in their place has a few > other ones. This thus requires a separate compatible to handle the > binding differences. The hardware however does have a chip ID register > that can be used to differentiate the variants within the driver. Thus > a fallback compatible to the base (MT6358) model is included. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [02/12] regulator: dt-bindings: mt6358: Convert to DT schema commit: 93880f7e5c8c864309a57c47669ac0bc432524d5 [03/12] regulator: dt-bindings: mt6358: Add regulator-allowed-modes property commit: 0bf4b56b5ecaf711865f313476f91c18338307bb [04/12] regulator: dt-bindings: mt6358: Add regulator supplies commit: 2f384e60acbac140732367d037c5f08db21513a0 [05/12] regulator: dt-bindings: mt6358: Add MT6366 PMIC commit: c631494a69c55301a03af9c028892c9098019652 [06/12] regulator: mt6358: Use mt6397-regulator.h binding header for buck mode macros commit: 9f3bec54d06f1eb4b47c7f78ef1401bc71977e9e [07/12] regulator: mt6358: Add supply names for MT6358 regulators commit: 3dfa8a7071d4e748d5a59566f9a96e381a9fccb2 [08/12] regulator: mt6358: fix and drop type prefix in MT6366 regulator node names commit: 0c3697b8980dd44df05ed77222c09bd8fe729626 [09/12] regulator: mt6358: Make MT6366 vcn18 LDO configurable commit: b7f3b89848b3bae3b1e3a97e75b82c65a4952cfc [10/12] regulator: mt6358: Add missing regulators for MT6366 commit: b7768e67af9a5b6d6101cbfc146969fedf8df4be [11/12] regulator: mt6358: Add supply names for MT6366 regulators commit: ce8ab92e66ccc99591b9cbb6630d720d5e6ad6ec 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
