linux-kernel - Re: [PATCH V3 1/4] dt-bindings: mmc: Add dll-hsr-list for HS400 and HS200 modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2bed4569-27a9-4173-af32-e6016c88f2c9@kernel.org>
Date: Tue, 10 Jun 2025 15:12:31 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ram Prakash Gupta <quic_rampraka@...cinc.com>,
 Sachin Gupta <quic_sachgupt@...cinc.com>,
 Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>
Cc: linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 quic_cang@...cinc.com, quic_nguyenb@...cinc.com, quic_bhaskarv@...cinc.com,
 quic_mapa@...cinc.com, quic_nitirawa@...cinc.com, quic_sartgarg@...cinc.com,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Subject: Re: [PATCH V3 1/4] dt-bindings: mmc: Add dll-hsr-list for HS400 and
 HS200 modes

On 10/06/2025 15:07, Ram Prakash Gupta wrote:
> 
> On 6/10/2025 6:23 PM, Krzysztof Kozlowski wrote:
>> On 10/06/2025 14:07, Ram Prakash Gupta wrote:
>>> Hi Krzysztof,
>>>
>>> Thanks for your comment, The Qualcomm Engineer who initiated this work,
>>> is no longer working on this and I am taking up the responsibility to continue
>>> on this work. I have started to check this and will start with addressing your
>>> comment next.
>>>
>>> Thanks,
>>> Ram
>>>
>>> On 1/22/2025 3:56 PM, Krzysztof Kozlowski wrote:
>>>> On 22/01/2025 10:47, Sachin Gupta wrote:
>> Above timeline is interesting:
>> 1. Patch sent on 22nd January.
>> 2. I provided comments few hours later, the same day.
>> 3. Silence.
>> 4. Employee changes job.
>> 5. Five months later...
>>
>> Not your fault Ram of course, but above timeline is not a responsible
>> way of upstreaming patches.
>>
>> Best regards,
>> Krzysztof
> 
> my apologies for this, I will give inputs internally to improve process
> for changing hands.


Not your fault, don't worry.

Best regards,
Krzysztof