mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <mani@kernel.org>,
	<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
	<bvanassche@acm.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <andersson@kernel.org>,
	<konradybcio@kernel.org>, <agross@kernel.org>,
	<James.Bottomley@HansenPartnership.com>,
	<martin.petersen@oracle.com>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/4] dt-bindings: ufs: qcom: Document MCQ register space for UFS
Date: Mon, 11 Aug 2025 21:42:29 +0530	[thread overview]
Message-ID: <adb94e86-38a2-4456-9363-d02c487ff7b8@quicinc.com> (raw)
In-Reply-To: <f8405e89-9449-4564-82d1-3146d9b75655@kernel.org>



On 11-Aug-25 8:12 PM, Krzysztof Kozlowski wrote:
> On 11/08/2025 16:31, Ram Kumar Dwivedi wrote:
>> Document Multi-Circular Queue (MCQ) register space for
>> Qualcomm UFS controllers.
>>
>> Signed-off-by: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>> ---
>>  .../devicetree/bindings/ufs/qcom,ufs.yaml        | 16 ++++++++++------
>>  1 file changed, 10 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
>> index 6c6043d9809e..daf681b0e23b 100644
>> --- a/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
>> +++ b/Documentation/devicetree/bindings/ufs/qcom,ufs.yaml
>> @@ -89,9 +89,13 @@ properties:
>>      maxItems: 2
>>  
>>    reg-names:
>> -    items:
>> -      - const: std
>> -      - const: ice
>> +    oneOf:
>> +      - items:
>> +          - const: std
>> +          - const: ice
>> +      - items:
>> +          - const: ufs_mem
>> +          - const: mcq
> 
> No. Why are you sending this? You have been Cc-ed here:
> 
> https://lore.kernel.org/all/20250731-dt-bindings-ufs-qcom-v2-3-53bb634bf95a@linaro.org/

Hi Krzysztof,

I understand I was Cc-ed on the patch thread you linked. However, if I send my patch on top of yours before it’s merged, the kernel bot might flag it due to missing base changes. Please let me know if you're okay with that — I can proceed with pushing my patch on top of yours.

Thanks,
Ram.


> 
> Above is neither correct nor aligned with what I told you.
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-08-11 16:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 14:31 [PATCH V2 0/4] Enable UFS MCQ support for SM8650 and SM8750 Ram Kumar Dwivedi
2025-08-11 14:31 ` [PATCH V2 1/4] dt-bindings: ufs: qcom: Document MCQ register space for UFS Ram Kumar Dwivedi
2025-08-11 14:42   ` Krzysztof Kozlowski
2025-08-11 16:12     ` Ram Kumar Dwivedi [this message]
2025-08-11 17:10       ` Krzysztof Kozlowski
2025-08-11 15:02   ` Bjorn Andersson
2025-08-11 16:52     ` Ram Kumar Dwivedi
2025-08-11 17:11     ` Krzysztof Kozlowski
2025-08-11 14:31 ` [PATCH V2 2/4] arm64: dts: qcom: sm8650: Enable MCQ support for UFS controller Ram Kumar Dwivedi
2025-08-11 14:43   ` Krzysztof Kozlowski
2025-08-11 16:54     ` Ram Kumar Dwivedi
2025-08-11 17:13       ` Krzysztof Kozlowski
2025-08-12 10:55       ` Dmitry Baryshkov
2025-08-12 15:23         ` Ram Kumar Dwivedi
2025-08-11 14:31 ` [PATCH V2 3/4] arm64: dts: qcom: sm8750: " Ram Kumar Dwivedi
2025-08-11 14:31 ` [PATCH V2 4/4] ufs: ufs-qcom: Streamline UFS MCQ resource mapping 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=adb94e86-38a2-4456-9363-d02c487ff7b8@quicinc.com \
    --to=quic_rdwivedi@quicinc.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agross@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=andersson@kernel.org \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=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®