From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 00/13] arm: dts: qcom: Switch to undeprecated qcom,calibration-variant
Date: Wed, 5 Mar 2025 07:48:04 +0100 [thread overview]
Message-ID: <64cb6810-4a75-4313-8d66-d773798f5a1b@linaro.org> (raw)
In-Reply-To: <d5l3bsozn2sauenlyjolb45hqgiiachixxycziuyfsxch3ypvd@mjb6whdyjztw>
On 04/03/2025 21:50, Dmitry Baryshkov wrote:
> On Tue, Mar 04, 2025 at 11:00:10AM -0600, Bjorn Andersson wrote:
>>
>> On Tue, 25 Feb 2025 10:58:57 +0100, Krzysztof Kozlowski wrote:
>>> Dependency
>>> ==========
>>> RFC, because this should be merged release after driver support is
>>> merged:
>>> https://lore.kernel.org/linux-devicetree/20250225-b-wifi-qcom-calibration-variant-v1-0-3b2aa3f89c53@linaro.org/T/#t
>>>
>>> Change will affect out of tree users, like other projects, of this DTS.
>>>
>>> [...]
>>
>> Applied, thanks!
>
> Applying it too early might break WiFi on those boards. I think
It is just non-bisectable, so that's why I put above remark.
> Krzysztof explicitly asked for it to be merged in +1 release, when the
> driver changes are in.
Yeah, that was the point.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-05 6:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 9:58 Krzysztof Kozlowski
2025-02-25 9:58 ` [PATCH RFC 01/13] ARM: dts: qcom: ipq4018: " Krzysztof Kozlowski
2025-02-25 9:58 ` [PATCH RFC 02/13] arm64: dts: qcom: msm8998: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 03/13] arm64: dts: qcom: qrb2210-rb1: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 04/13] arm64: dts: qcom: qrb4210-rb2: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 05/13] arm64: dts: qcom: sc7180: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 06/13] arm64: dts: qcom: sdm845: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 07/13] arm64: dts: qcom: sda660-ifc6560: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 08/13] arm64: dts: qcom: sm6115: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 09/13] arm64: dts: qcom: sm8150-hdk: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 10/13] arm64: dts: qcom: qcm6490: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 11/13] arm64: dts: qcom: sa8775p-ride: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 12/13] arm64: dts: qcom: sc8280xp: " Krzysztof Kozlowski
2025-02-25 9:59 ` [PATCH RFC 13/13] arm64: dts: qcom: sm8250-elish: " Krzysztof Kozlowski
2025-02-25 10:30 ` [PATCH RFC 00/13] arm: dts: qcom: " Konrad Dybcio
2025-03-04 17:00 ` Bjorn Andersson
2025-03-04 20:50 ` Dmitry Baryshkov
2025-03-05 6:48 ` Krzysztof Kozlowski [this message]
2025-03-06 18:16 ` Jeff Johnson
2025-03-06 19:14 ` Dmitry Baryshkov
2025-03-28 7:50 ` Krzysztof Kozlowski
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=64cb6810-4a75-4313-8d66-d773798f5a1b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@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®