From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH V3 4/5] arm64: dts: qcom: sm8650: Enable MCQ support for UFS controller
Date: Mon, 1 Sep 2025 10:05:56 +0200 [thread overview]
Message-ID: <b049c4be-f3c1-49e4-8737-c29c52185e60@kernel.org> (raw)
In-Reply-To: <aonf4hobz6b3a75lwiblu44gxvae4hnp2mcnh5sqlyzo6k7hwe@a5toymspbkdy>
On 01/09/2025 06:15, Manivannan Sadhasivam wrote:
>>>>
>>>> I don't understand why you combine DTS patch into UFS patchset. This
>>>> creates impression of dependent work, which would be a trouble for merging.
>>>>
>>>
>>> What trouble? Even if the DTS depends on the driver/bindings change, can't it
>>> still go through a different tree for the same cycle? It happened previously as
>>
>> It all depends on sort of dependency.
>>
>>> well, unless the rule changed now.
>>
>> No, the point is that there is absolutely nothing relevant between the
>> DTS and drivers here. Combining unrelated patches, completely different
>> ones, targeting different subsystems into one patchset was always a
>> mistake. This makes only life of maintainers more difficult, for no gain.
>>
>
> Ok. Since patch 2 is just a refactoring, it should not be required for enabling
> MCQ. But it is not clear if that is the case.
>
> @Ram/Nitin: Please confirm if MCQ can be enabled without patch 2. If yes, then
> post the DTS separately, otherwise, you need to rewrite the commit message of
> patch 2 to state it explicitly.
Dependency of DTS on driver would be another issue and in any case must
be clearly documented, not implicit via patch order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-01 8:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 11:23 [PATCH V3 0/5] Enable UFS MCQ support for SM8650 and SM8750 Ram Kumar Dwivedi
2025-08-21 11:23 ` [PATCH V3 1/5] ufs: ufs-qcom: Streamline UFS MCQ resource mapping Ram Kumar Dwivedi
2025-08-22 9:04 ` Manivannan Sadhasivam
2025-09-03 7:27 ` Nitin Rawat
2025-08-21 11:24 ` [PATCH V3 2/5] ufs: ufs-qcom: Refactor MCQ register dump logic Ram Kumar Dwivedi
2025-08-22 9:08 ` Manivannan Sadhasivam
2025-08-22 17:49 ` Ram Kumar Dwivedi
2025-08-21 11:24 ` [PATCH V3 3/5] scsi: ufs: core: Remove unused ufshcd_res_info structure Ram Kumar Dwivedi
2025-08-21 11:48 ` Krzysztof Kozlowski
2025-09-01 16:08 ` Nitin Rawat
2025-09-02 6:18 ` Krzysztof Kozlowski
2025-09-03 13:28 ` Manivannan Sadhasivam
2025-09-03 13:34 ` Nitin Rawat
2025-08-21 11:24 ` [PATCH V3 4/5] arm64: dts: qcom: sm8650: Enable MCQ support for UFS controller Ram Kumar Dwivedi
2025-08-21 11:49 ` Krzysztof Kozlowski
2025-08-29 16:18 ` Manivannan Sadhasivam
2025-08-30 8:43 ` Krzysztof Kozlowski
2025-09-01 4:15 ` Manivannan Sadhasivam
2025-09-01 8:05 ` Krzysztof Kozlowski [this message]
2025-09-01 14:50 ` Nitin Rawat
2025-08-21 11:24 ` [PATCH V3 5/5] arm64: dts: qcom: sm8750: " Ram Kumar Dwivedi
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=b049c4be-f3c1-49e4-8737-c29c52185e60@kernel.org \
--to=krzk@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_rdwivedi@quicinc.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).