[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9dfd2eb2-fda7-4f29-881b-e1c4a2b3f6fc@kernel.org>
Date: Mon, 18 Aug 2025 11:55:33 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@....qualcomm.com>,
Georgi Djakov <djakov@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Sibi Sankar
<quic_sibis@...cinc.com>, Odelu Kukatla <quic_okukatla@...cinc.com>,
Mike Tipton <mike.tipton@....qualcomm.com>,
Imran Shaik <quic_imrashai@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: interconnect: Add OSM L3 compatible
for QCS615 SoC
On 18/08/2025 11:12, Raviteja Laggyshetty wrote:
>>> .../devicetree/bindings/interconnect/qcom,osm-l3.yaml | 5 +++++
>>> 1 file changed, 5 insertions(+)
>> No, slow down, this conflicts with other patch and makes your entry
>> duplicated. Just squash both commits.
>>
> The conflicting patch
> https://lore.kernel.org/all/20250711102540.143-2-raviteja.laggyshetty@oss.qualcomm.com/
> got picked into v6.17-rc1.
Then why you could not rebase on next if you sent it afterwards? You are
not making the process easier for us.
Best regards,
Krzysztof
Powered by blists - more mailing lists