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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3b75fe83-85c5-f0d3-c5db-481ef133d6de@quicinc.com>
Date: Tue, 10 Jun 2025 18:37:12 +0530
From: Ram Prakash Gupta <quic_rampraka@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
        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>,
        Bhupesh Sharma <bhupesh.sharma@...aro.org>
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>
Subject: Re: [PATCH V3 1/4] dt-bindings: mmc: Add dll-hsr-list for HS400 and
 HS200 modes


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.