[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159844655479.37260.3133336814672440468.b4-ty@kernel.org>
Date: Wed, 26 Aug 2020 13:55:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Gene Chen <gene.chen.richtek@...il.com>, matthias.bgg@...il.com,
robh+dt@...nel.org
Cc: linux-kernel@...r.kernel.org, lgirdwood@...il.com,
benjamin.chao@...iatek.com, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, gene_chen@...htek.com,
cy_huang@...htek.com, shufan_lee@...htek.com,
Wilma.Wu@...iatek.com, devicetree@...r.kernel.org
Subject: Re: [PATCH v4 0/2] regulator: mt6360: Add support for MT6360 regulator
On Wed, 26 Aug 2020 18:49:16 +0800, Gene Chen wrote:
> This patch series add MT6360 regulator support contains driver and binding document
>
> Gene Chen (2)
> regulator: mt6360: Add support for MT6360 regulator
> dt-bindings: regulator: mt6360: Add DT binding
>
> Documentation/devicetree/bindings/regulator/mt6360-regulator.yaml | 113 ++
> drivers/regulator/Kconfig | 9
> drivers/regulator/Makefile | 1
> drivers/regulator/mt6360-regulator.c | 459 ++++++++++
> include/dt-bindings/regulator/mediatek,mt6360-regulator.h | 16
> 5 files changed, 598 insertions(+)
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] regulator: mt6360: Add support for MT6360 regulator
commit: d321571d5e4c2d5511b75e6cf1a910e0a0c2a2e9
[2/2] dt-bindings: regulator: mt6360: Add DT binding documentation
commit: 9b1d3422e16ffcd4dad7729459717b216490540d
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