[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bcc1ee7-2f43-4fa5-898f-7bddfe7b1a10@kernel.org>
Date: Mon, 11 Aug 2025 19:10:37 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ram Kumar Dwivedi <quic_rdwivedi@...cinc.com>, mani@...nel.org,
alim.akhtar@...sung.com, avri.altman@....com, bvanassche@....org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
andersson@...nel.org, konradybcio@...nel.org, agross@...nel.org,
James.Bottomley@...senPartnership.com, martin.petersen@...cle.com
Cc: linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/4] dt-bindings: ufs: qcom: Document MCQ register
space for UFS
On 11/08/2025 18:12, Ram Kumar Dwivedi wrote:
>>> + - 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.
I don't understand it. We discuss this patch. What is with that
conditional "if I send"? You already sent it.
Please wrap your replies to match mailing list style.
Best regards,
Krzysztof
Powered by blists - more mailing lists