From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
Mike Tipton <mike.tipton@oss.qualcomm.com>,
Imran Shaik <quic_imrashai@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: interconnect: Add OSM L3 compatible for QCS615 SoC
Date: Mon, 18 Aug 2025 11:55:33 +0200 [thread overview]
Message-ID: <9dfd2eb2-fda7-4f29-881b-e1c4a2b3f6fc@kernel.org> (raw)
In-Reply-To: <14d0e02e-350c-42bc-93b5-c81e11b3bd5d@oss.qualcomm.com>
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
next prev parent reply other threads:[~2025-08-18 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 6:15 [PATCH V2 0/2] Add OSM L3 provider support on QCS615 SoC Raviteja Laggyshetty
2025-08-04 6:15 ` [PATCH V2 1/2] dt-bindings: interconnect: Add OSM L3 compatible for " Raviteja Laggyshetty
2025-08-04 6:26 ` Krzysztof Kozlowski
2025-08-18 9:12 ` Raviteja Laggyshetty
2025-08-18 9:55 ` Krzysztof Kozlowski [this message]
2025-08-04 6:15 ` [PATCH V2 2/2] arm64: dts: qcom: qcs615: Add OSM l3 interconnect provider node and CPU OPP tables to scale DDR/L3 Raviteja Laggyshetty
2025-08-04 6:28 ` Dmitry Baryshkov
2025-08-18 6:52 ` Raviteja Laggyshetty
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=9dfd2eb2-fda7-4f29-881b-e1c4a2b3f6fc@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike.tipton@oss.qualcomm.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--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).