All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Harrison Vanderbyl <harrison.vanderbyl@gmail.com>
Cc: marcus@nazgul.ch, kirill@korins.ky, vkoul@kernel.org,
	kishon@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, mani@kernel.org, alim.akhtar@samsung.com,
	avri.altman@wdc.com, bvanassche@acm.org, agross@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] dts: describe x1e80100 ufs
Date: Thu, 14 Aug 2025 13:18:46 +0200	[thread overview]
Message-ID: <433e1189-e2b6-4299-9fa7-13e7994ec89c@kernel.org> (raw)
In-Reply-To: <aa0ed59a-4eb6-4f7f-b430-4976ee9724d8@oss.qualcomm.com>

On 14/08/2025 11:46, Konrad Dybcio wrote:
> On 8/14/25 8:59 AM, Krzysztof Kozlowski wrote:
>> On 14/08/2025 04:42, Bjorn Andersson wrote:
>>> On Thu, Aug 14, 2025 at 10:59:04AM +1000, Harrison Vanderbyl wrote:
>>>
>>> Welcome to LKML, Harrison. Some small things to improve.
>>>
>>> Please extend the subject prefix to match other changes in the files of
>>> each patch, e.g. this one would be "arm64: dts: qcom: x1e80100: ".
>>>
>>> "git log --oneline -- file" is your friend here.
>>>
>>>> Describe device tree entry for x1e80100 ufs device
>>
>> This is duplicating earlier patches:
>> https://lore.kernel.org/all/szudb2teaacchrp4kn4swkqkoplgi5lbw7vbqtu5vhds4qat62@2tciswvelbmu/
> 
> (that submitter clearly expressed lack of interest in proceeding)
> 

Sure, would be good though to reflect that - provide summary of previous
discussions, changelogs or at least give links.

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Harrison Vanderbyl <harrison.vanderbyl@gmail.com>
Cc: marcus@nazgul.ch, kirill@korins.ky, vkoul@kernel.org,
	kishon@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, mani@kernel.org, alim.akhtar@samsung.com,
	avri.altman@wdc.com, bvanassche@acm.org, agross@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] dts: describe x1e80100 ufs
Date: Thu, 14 Aug 2025 13:18:46 +0200	[thread overview]
Message-ID: <433e1189-e2b6-4299-9fa7-13e7994ec89c@kernel.org> (raw)
In-Reply-To: <aa0ed59a-4eb6-4f7f-b430-4976ee9724d8@oss.qualcomm.com>

On 14/08/2025 11:46, Konrad Dybcio wrote:
> On 8/14/25 8:59 AM, Krzysztof Kozlowski wrote:
>> On 14/08/2025 04:42, Bjorn Andersson wrote:
>>> On Thu, Aug 14, 2025 at 10:59:04AM +1000, Harrison Vanderbyl wrote:
>>>
>>> Welcome to LKML, Harrison. Some small things to improve.
>>>
>>> Please extend the subject prefix to match other changes in the files of
>>> each patch, e.g. this one would be "arm64: dts: qcom: x1e80100: ".
>>>
>>> "git log --oneline -- file" is your friend here.
>>>
>>>> Describe device tree entry for x1e80100 ufs device
>>
>> This is duplicating earlier patches:
>> https://lore.kernel.org/all/szudb2teaacchrp4kn4swkqkoplgi5lbw7vbqtu5vhds4qat62@2tciswvelbmu/
> 
> (that submitter clearly expressed lack of interest in proceeding)
> 

Sure, would be good though to reflect that - provide summary of previous
discussions, changelogs or at least give links.

Best regards,
Krzysztof

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2025-08-14 11:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  0:59 [PATCH 0/3] Describe x1e80100 ufs Harrison Vanderbyl
2025-08-14  0:59 ` Harrison Vanderbyl
2025-08-14  0:59 ` [PATCH 1/3] dt-bindings: describe " Harrison Vanderbyl
2025-08-14  0:59   ` Harrison Vanderbyl
2025-08-14  6:56   ` Dmitry Baryshkov
2025-08-14  6:56     ` Dmitry Baryshkov
2025-08-14  0:59 ` [PATCH 2/3] ufs: ufs-qcom: describe x1e80100 quirks Harrison Vanderbyl
2025-08-14  0:59   ` Harrison Vanderbyl
2025-08-14  6:57   ` Dmitry Baryshkov
2025-08-14  6:57     ` Dmitry Baryshkov
2025-08-14  6:59   ` Krzysztof Kozlowski
2025-08-14  6:59     ` Krzysztof Kozlowski
2025-08-14  0:59 ` [PATCH 3/3] dts: describe x1e80100 ufs Harrison Vanderbyl
2025-08-14  0:59   ` Harrison Vanderbyl
2025-08-14  2:42   ` Bjorn Andersson
2025-08-14  2:42     ` Bjorn Andersson
2025-08-14  6:59     ` Krzysztof Kozlowski
2025-08-14  6:59       ` Krzysztof Kozlowski
2025-08-14  9:46       ` Konrad Dybcio
2025-08-14  9:46         ` Konrad Dybcio
2025-08-14 11:18         ` Krzysztof Kozlowski [this message]
2025-08-14 11:18           ` Krzysztof Kozlowski
2025-08-14 11:26           ` Dmitry Baryshkov
2025-08-14 11:26             ` Dmitry Baryshkov
2025-08-14 13:57             ` Bjorn Andersson
2025-08-14 13:57               ` Bjorn Andersson
2025-08-14  7:20   ` Nitin Rawat
2025-08-14  7:20     ` Nitin Rawat
2025-08-25  8:10     ` Manivannan Sadhasivam
2025-08-25  8:10       ` Manivannan Sadhasivam
2025-08-14  9:27 ` [PATCH 0/3] Describe " Konrad Dybcio
2025-08-14  9:27   ` Konrad Dybcio
2025-08-15 21:19 ` Rob Herring (Arm)
2025-08-15 21:19   ` Rob Herring (Arm)
  -- strict thread matches above, loose matches on Subject: below --
2025-08-14 19:31 [PATCH 3/3] dts: describe " kernel test robot
2025-08-14 21:48 kernel test robot

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=433e1189-e2b6-4299-9fa7-13e7994ec89c@kernel.org \
    --to=krzk@kernel.org \
    --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=harrison.vanderbyl@gmail.com \
    --cc=kirill@korins.ky \
    --cc=kishon@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-phy@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=marcus@nazgul.ch \
    --cc=robh@kernel.org \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.