Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Yijie Yang <yijie.yang@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK
Date: Mon, 19 Jan 2026 14:52:53 +0100	[thread overview]
Message-ID: <8cea513d-c1b5-41b0-9455-abff0aec3c36@oss.qualcomm.com> (raw)
In-Reply-To: <f54f4eda-5776-4a68-a661-b66619ef9041@oss.qualcomm.com>

On 1/19/26 2:51 PM, Krzysztof Kozlowski wrote:
> On 19/01/2026 14:35, Konrad Dybcio wrote:
>> On 1/19/26 7:54 AM, Yijie Yang wrote:
>>>
>>>
>>> On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote:
>>>> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote:
>>
>> [...]
>>
>>>>>>> Changes in v4:
>>>>>>> - EDITME: describe what is new in this series revision.
>>>>>>> - EDITME: use bulletpoints and terse descriptions.
>>>>>>
>>>>>> Oh no. B4 probably even warned you about not sending it out.
>>>>>>
>>>>>>   From this changelog I can assume that nothing has changed. Is it
>>>>>> correct?
>>>>>
>>>>> This section was generated automatically by b4 and was not reviewed
>>>>> carefully. The actual list of changes is in the section below.
>>>>
>>>> But why????? Why do you ignore what was done for you and write it on
>>>> your own, reversing the order, etc? And even if you decided to ignore it
>>>> for any reason, why didn't you delete it?
>>>
>>> The confusion was caused by mixing b4 and git format-patch to handle fine‑grained patch formatting. The Git configuration Konrad suggested did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 to track the upstream thread, which caused this section to be generated automatically. I did not notice this and mistakenly re‑wrote it myself.
>>
>> I found that I have additional options set in my *local* gitconfig:
>>
>> [diff]
>>         renameLimit = 999999
>>         rename = true
> 
> This one does not exist. You wanted "renames" but you set it two lines
> below.

thanks

Konrad

  reply	other threads:[~2026-01-19 13:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 10:41 [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-16 10:41 ` [PATCH v4 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-16 10:41 ` [PATCH v4 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-16 10:41 ` [PATCH v4 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-20 12:44   ` Konrad Dybcio
2026-01-16 10:41 ` [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-16 16:19   ` Krzysztof Kozlowski
2026-01-19  3:13     ` Yijie Yang
2026-01-19  6:33       ` Dmitry Baryshkov
2026-01-19  7:10         ` Yijie Yang
2026-01-19  8:48         ` Yijie Yang
2026-01-19  9:46           ` Dmitry Baryshkov
2026-01-19 10:42             ` Yijie Yang
2026-01-19 13:31             ` Konrad Dybcio
2026-01-20  6:47               ` Yijie Yang
2026-01-19  7:05       ` Krzysztof Kozlowski
2026-01-20  6:49         ` Yijie Yang
2026-01-20  7:17           ` Krzysztof Kozlowski
2026-01-20  7:55             ` Yijie Yang
2026-01-19 13:53   ` Konrad Dybcio
2026-01-20  7:01     ` Yijie Yang
2026-01-16 11:31 ` [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK Dmitry Baryshkov
2026-01-19  2:39   ` Yijie Yang
2026-01-19  6:34     ` Dmitry Baryshkov
2026-01-19  6:54       ` Yijie Yang
2026-01-19 13:35         ` Konrad Dybcio
2026-01-19 13:51           ` Krzysztof Kozlowski
2026-01-19 13:52             ` Konrad Dybcio [this message]
2026-01-20  7:14               ` Yijie Yang
2026-01-16 15:40 ` Rob Herring

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=8cea513d-c1b5-41b0-9455-abff0aec3c36@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=yijie.yang@oss.qualcomm.com \
    /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