[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168053447680.47740.2062036242012042206.b4-ty@kernel.org>
Date: Mon, 03 Apr 2023 16:07:56 +0100
From: Mark Brown <broonie@...nel.org>
To: Bjorn Andersson <andersson@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Georgi Djakov <djakov@...nel.org>,
Vinod Koul <vkoul@...nel.org>
Cc: linux-arm-msm@...r.kernel.org,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Bart Van Assche <bvanassche@....org>,
Thomas Gleixner <tglx@...utronix.de>,
Marc Zyngier <maz@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Krzysztof WilczyĆski <kw@...ux.com>,
linux-pci@...r.kernel.org,
Kishon Vijay Abraham I <kishon@...nel.org>,
linux-phy@...ts.infradead.org,
Wesley Cheng <quic_wcheng@...cinc.com>,
linux-usb@...r.kernel.org, linux-pm@...r.kernel.org,
linux-scsi@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>
Subject: Re: (subset) [PATCH v2 00/12] Introduce the SC8180x devices
On Sat, 25 Mar 2023 17:54:32 +0530, Vinod Koul wrote:
> This introduces Qualcomm SC8180x SoC which features in Lenovo Flex 5G
> laptop. This also adds support for Primus platform as well as Lenovo Flex 5G
> laptop.
>
> I would be great if submaintainers can ack the binding patch so that
> everything can go thru qcom tree
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[08/12] regulator: dt-bindings: qcom,rpmh: Add compatible for PMC8180
commit: fc4fef625decc80cf3a72e884a4e37288bfa0f9b
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