From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Herring <robh@kernel.org>, Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [GIT PULL] dt-bindings: qcom for v5.20, version 2
Date: Wed, 20 Jul 2022 18:33:35 +0200 [thread overview]
Message-ID: <5229adbc-ec5f-259f-0fd1-1df6e979c9bb@linaro.org> (raw)
In-Reply-To: <Ytgf7ejB/2usK4uW@builder.lan>
On 20/07/2022 17:31, Bjorn Andersson wrote:
> On Tue 28 Jun 04:22 CDT 2022, Krzysztof Kozlowski wrote:
> [..]
>> The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
>>
>> Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
>>
>> are available in the Git repository at:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-dt.git tags/dt-bindings-qcom-5.20-2
>>
>> for you to fetch changes up to 062529700fdb843eee921961eb3cbc6a51419491:
>>
>> dt-bindings: cpufreq: qcom-cpufreq-nvmem: fix board compatible in example (2022-06-28 10:28:50 +0200)
>>
>> ----------------------------------------------------------------
>> Devicetree bindings for Qualcomm for v5.20
>>
>> Cleanup, fixes and additions of missing pieces for Qualcomm bindings.
>> These are address dtbs_check warnings and do not bring new hardware
>> (new compatibles are added for existing boards/hardware).
>>
>> ----------------------------------------------------------------
>> Krzysztof Kozlowski (25):
>
> Many thanks for gathering these patches in a pull request!
>
>> dt-bindings: soc: qcom,rpmh-rsc: simplify qcom,tcs-config
>> spi: dt-bindings: qcom,spi-geni-qcom: allow three interconnects
>
> This,
>
>> dt-bindings: soc: qcom: aoss: document qcom,sm8450-aoss-qmp
>> dt-bindings: soc: qcom: qcom,smd-rpm: add power-controller
>> dt-bindings: nvmem: qfprom: add IPQ8064 and SDM630 compatibles
>
> this,
>
>> dt-bindings: leds: qcom-wled: fix number of addresses
>
> this
Although it is preferred that such subsystem patches go via subsystem
trees, but subsystem maintainers sometimes do not pick up DT binding
patches. Maybe they expect Rob will pick them up or sub-arch maintainer.
I don't know. I just see the result that they wait for months (like [1]
was waiting for ~1.5 months)
If you don't want to take them, even though these are fixes, I will try
to poke the maintainers.
>
>> dt-bindings: arm: qcom: fix Alcatel OneTouch Idol 3 compatibles
>> dt-bindings: arm: qcom: fix Longcheer L8150 compatibles
>> dt-bindings: arm: qcom: fix MSM8916 MTP compatibles
>> dt-bindings: arm: qcom: fix MSM8994 boards compatibles
>> dt-bindings: arm: qcom: add missing MSM8916 board compatibles
>> dt-bindings: arm: qcom: add missing MSM8994 board compatibles
>> dt-bindings: arm: qcom: add missing SM8150 board compatibles
>> dt-bindings: arm: qcom: add missing SM8250 board compatibles
>> dt-bindings: arm: qcom: add missing SM8350 board compatibles
>> dt-bindings: vendor-prefixes: add Shift GmbH
>> dt-bindings: arm: qcom: add missing MSM8998 board compatibles
>> dt-bindings: arm: qcom: add missing MSM8992 board compatibles
>> dt-bindings: arm: qcom: add missing QCS404 board compatibles
>> dt-bindings: arm: qcom: add missing SDM630 board compatibles
>> dt-bindings: arm: qcom: add missing SDM636 board compatibles
>> dt-bindings: arm: qcom: add missing SDM845 board compatibles
>> dt-bindings: arm: qcom: add missing SM6125 board compatibles
>> dt-bindings: arm: qcom: add missing SM6350 board compatibles
>> dt-bindings: cpufreq: qcom-cpufreq-nvmem: fix board compatible in example
>
> and this does however need to go through respective maintainers' trees.
However this one last should go via your tree, as expressed by Rob (and
acked by Viresh) in [2]. It fixes the issue which is exposed by
dt-bindings/arm/qcom change (not caused by visible because of).
[1]
https://lore.kernel.org/all/20220505154702.422108-1-krzysztof.kozlowski@linaro.org/
[2] https://lore.kernel.org/all/20220627195040.GA2840123-robh@kernel.org/
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-20 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:22 [GIT PULL] dt-bindings: qcom for v5.20, version 2 Krzysztof Kozlowski
2022-07-20 15:31 ` Bjorn Andersson
2022-07-20 16:33 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5229adbc-ec5f-259f-0fd1-1df6e979c9bb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).