linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ram Prakash Gupta <quic_rampraka@quicinc.com>,
	Sachin Gupta <quic_sachgupt@quicinc.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	quic_cang@quicinc.com, quic_nguyenb@quicinc.com,
	quic_bhaskarv@quicinc.com, quic_mapa@quicinc.com,
	quic_nitirawa@quicinc.com, quic_sartgarg@quicinc.com,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH V3 1/4] dt-bindings: mmc: Add dll-hsr-list for HS400 and HS200 modes
Date: Tue, 10 Jun 2025 15:12:31 +0200	[thread overview]
Message-ID: <2bed4569-27a9-4173-af32-e6016c88f2c9@kernel.org> (raw)
In-Reply-To: <3b75fe83-85c5-f0d3-c5db-481ef133d6de@quicinc.com>

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

  reply	other threads:[~2025-06-10 13:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  9:47 [PATCH V3 0/4] mmc: sdhci-msm: Rectify DLL programming sequence for SDCC Sachin Gupta
2025-01-22  9:47 ` [PATCH V3 1/4] dt-bindings: mmc: Add dll-hsr-list for HS400 and HS200 modes Sachin Gupta
2025-01-22 10:26   ` Krzysztof Kozlowski
     [not found]     ` <e0f43fc7-2f38-335d-1515-c97594a55566@quicinc.com>
2025-06-10 12:53       ` Krzysztof Kozlowski
2025-06-10 13:07         ` Ram Prakash Gupta
2025-06-10 13:12           ` Krzysztof Kozlowski [this message]
2025-06-26 14:16     ` Ram Prakash Gupta
2025-06-26 14:24       ` Ram Prakash Gupta
2025-06-26 17:42       ` Krzysztof Kozlowski
2025-06-27  6:48         ` Ram Prakash Gupta
2025-06-27 13:57         ` Konrad Dybcio
2025-06-27 14:50           ` Krzysztof Kozlowski
2025-06-30  6:33             ` Ram Prakash Gupta
2025-01-22 11:26   ` Rob Herring (Arm)
2025-01-22  9:47 ` [PATCH V3 2/4] mmc: sdhci-msm: Add core_major, minor to msm_host structure Sachin Gupta
2025-01-22  9:55   ` Dmitry Baryshkov
2025-01-22  9:47 ` [PATCH V3 3/4] mmc: sdhci-msm: Add Device tree parsing logic for DLL settings Sachin Gupta
2025-01-22  9:57   ` Dmitry Baryshkov
2025-06-10 12:17     ` Ram Prakash Gupta
2025-07-23 10:14       ` Ram Prakash Gupta
2025-07-23 10:37         ` Konrad Dybcio
2025-07-23 12:02           ` Ram Prakash Gupta
2025-01-22  9:47 ` [PATCH V3 4/4] mmc: sdhci-msm: Rectify DLL programming sequence for SDCC Sachin Gupta
2025-01-22 10:00   ` Dmitry Baryshkov
2025-06-10 12:22     ` Ram Prakash Gupta
2025-06-10 13:38       ` Dmitry Baryshkov

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=2bed4569-27a9-4173-af32-e6016c88f2c9@kernel.org \
    --to=krzk@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=quic_bhaskarv@quicinc.com \
    --cc=quic_cang@quicinc.com \
    --cc=quic_mapa@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@quicinc.com \
    --cc=quic_rampraka@quicinc.com \
    --cc=quic_sachgupt@quicinc.com \
    --cc=quic_sartgarg@quicinc.com \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.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).