Message ID | 20230325122444.249507-1-vkoul@kernel.org |
---|---|
Headers | show |
Series | Introduce the SC8180x devices | expand |
On 25/03/2023 13:24, 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 I think Bjorn recently was rejecting taking bindings patches, so what changed? Best regards, Krzysztof
On Mon, Mar 27, 2023 at 09:46:31AM +0200, Krzysztof Kozlowski wrote: > On 25/03/2023 13:24, 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 > > I think Bjorn recently was rejecting taking bindings patches, so what > changed? > Nothing changed. In the interest of reducing the risk for merge conflicts I still think it's best if bindings goes via respective maintainer trees; so patch 1 is for me... Regards, Bjorn
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