From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: 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
Date: Tue, 28 Jun 2022 11:19:32 +0200 [thread overview]
Message-ID: <28eca0b2-930e-8688-6544-e6c13a809df8@linaro.org> (raw)
In-Reply-To: <20220623145837.456817-1-krzysztof.kozlowski@linaro.org>
On 23/06/2022 16:58, Krzysztof Kozlowski wrote:
> Hi Rob and Bjorn,
>
> I am fixing/improving quite a lot of Qualcomm bindings and I produced several
> separate patchsets. They wait on mailing list for quite a long time, in some
> cases two months, so I decided to grab all them and send in one organized pull.
>
> All patches here got Rob's ack.
>
> This also brings compatibles for Qualcomm boards, therefore it might be
> desirable to merge everything through Bjorn's tree, however at this point I
> want to just get it merged as fast as possible, because I am really afraid they
> will miss the v5.20 cycle. Therefore the pull is towards Rob, but maybe
> First-comes-first-served is also good approach.
>
> Best regards,
> Krzysztof
>
>
> 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
I'll prepare a second pull, including fix for cpufreq bindings.
https://lore.kernel.org/all/20220627143340.477120-1-krzysztof.kozlowski@linaro.org/
Best regards,
Krzysztof
prev parent reply other threads:[~2022-06-28 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 14:58 Krzysztof Kozlowski
2022-06-28 9:19 ` 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=28eca0b2-930e-8688-6544-e6c13a809df8@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
all inboxes | Powered by JetHome®