Received-SPF: pass (google.com: domain of linux-kernel+bounces-34144-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Mark Brown <broonie@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>, 
 Liam Girdwood <lgirdwood@gmail.com>, 
 Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20240109-rpm_vreg_cleanup-v3-1-fa0201029f78@linaro.org>
References: <20240109-rpm_vreg_cleanup-v3-1-fa0201029f78@linaro.org>
Subject: Re: [PATCH v3] regulator: qcom_smd: Keep one rpm handle for all
 vregs
Message-Id: <170595627643.145638.11249590166441157779.b4-ty@kernel.org>
Date: Mon, 22 Jan 2024 20:44:36 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Tue, 09 Jan 2024 11:04:49 +0100, Konrad Dybcio wrote:
> For no apparent reason (as there's just one RPM per SoC), all vregs
> currently store a copy of a pointer to smd_rpm. Introduce a single,
> global one to save up on space in each definition.
> 
> bloat-o-meter reports a slight uptick:
> 
> Total: Before=44008, After=44080, chg +0.16%
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: qcom_smd: Keep one rpm handle for all vregs
      commit: 5df3b41bd6b5432010d6d85e5aa7217bd8f6b0cb

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