[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4541415f-0e6d-438f-a7b3-0c29c196e432@collabora.com>
Date: Wed, 26 Jun 2024 09:43:36 +0200
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
To: Mark Brown <broonie@...nel.org>, djakov@...nel.org
Cc: robh@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
matthias.bgg@...il.com, lgirdwood@...il.com, gustavoars@...nel.org,
henryc.chen@...iatek.com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
kernel@...labora.com, wenst@...omium.org, amergnat@...libre.com,
Kees Cook <kees@...nel.org>
Subject: Re: (subset) [PATCH v6 0/7] MediaTek DVFSRC Bus Bandwidth and
Regulator knobs
Il 25/06/24 20:47, Mark Brown ha scritto:
> On Mon, 10 Jun 2024 10:57:28 +0200, AngeloGioacchino Del Regno wrote:
>> Changes in v6:
>> - Fixed build with clang (thanks Nathan!)
>> - Removed unused mtk_rmw() macro in mtk-dvfsrc.c
>> - Added MODULE_DESCRIPTION() to mtk-dvfsrc-regulator.c
>>
>> Changes in v5:
>> - Fixed Kconfig dependencies in interconnect
>> - Fixed module build for dvfsrc and interconnect
>>
>> [...]
>
> Applied to
>
Thanks Mark, appreciated :-)
Cheers
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
>
> Thanks!
>
> [1/7] dt-bindings: regulator: Add bindings for MediaTek DVFSRC Regulators
> commit: b147ae7ae5141cb10c520d372ecabb2c520210c4
> [5/7] regulator: Remove mtk-dvfsrc-regulator.c
> commit: cd102850e32c145661c6a0640dc6c5feba11af72
> [6/7] regulator: Add refactored mtk-dvfsrc-regulator driver
> commit: d2ea920a4092b3c0a6a004b93ce198ca37455d90
>
> 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