[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aeec2729-e610-f266-f336-847675cf85ec@linaro.org>
Date: Tue, 30 Aug 2022 12:32:04 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Johan Hovold <johan@...nel.org>, Vinod Koul <vkoul@...nel.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Kishon Vijay Abraham I <kishon@...com>,
linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/30] phy: qcom,qmp: fix dt-bindings and deprecate
lane suffix
On 30/08/2022 10:01, Johan Hovold wrote:
> On Tue, Aug 30, 2022 at 10:36:43AM +0530, Vinod Koul wrote:
>> On 14-07-22, 14:43, Johan Hovold wrote:
[skipped]
>>> The final patches add support for the updated binding to the (recently
>>> split up) PHY drivers. Included is also a related combo PHY cleanup.
>>
>> This fails at patch 2 for me on v6.0-rc1, please rebase and resend
>
> Are you sure you haven't applied anything to your local tree that causes
> this?
When doing the QMP split, we ended up in a similar situation if I
remember correctly. Most probably the easiest way is to provide a branch
for Vinod to pull in addition to the patches being sent to ML.
> I just tried fetching the v3 series from lore and it applies just fine
> on top of 6.0-rc1.
>
> Note that if you've added a new compatible string locally, the second
> patch which sorts the compatible strings is likely to fail to apply.
>
> Johan
--
With best wishes
Dmitry
Powered by blists - more mailing lists