linux-kernel - Re: [PATCH 08/12] arm64: defconfig: Enable NT37801 DSI panel driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4e444fd3-b079-4e0c-9449-1c119e1d710a@kernel.org>
Date: Thu, 30 Oct 2025 11:43:49 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: yuanjiey <yuanjie.yang@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>, robin.clark@....qualcomm.com,
 lumag@...nel.org, abhinav.kumar@...ux.dev, sean@...rly.run,
 marijn.suijten@...ainline.org, airlied@...il.com, simona@...ll.ch,
 maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
 robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 quic_mkrishn@...cinc.com, jonathan@...ek.ca, quic_khsieh@...cinc.com,
 neil.armstrong@...aro.org, linux-arm-msm@...r.kernel.org,
 dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 tingwei.zhang@....qualcomm.com, aiqun.yu@....qualcomm.com,
 yongxing.mou@....qualcomm.com
Subject: Re: [PATCH 08/12] arm64: defconfig: Enable NT37801 DSI panel driver

On 30/10/2025 08:07, yuanjiey wrote:
> On Thu, Oct 30, 2025 at 06:37:40AM +0100, Krzysztof Kozlowski wrote:
>> On 30/10/2025 03:33, yuanjiey wrote:
>>> On Wed, Oct 29, 2025 at 02:05:20PM +0100, Krzysztof Kozlowski wrote:
>>>> On 29/10/2025 03:37, yuanjiey wrote:
>>>>> On Mon, Oct 27, 2025 at 10:51:23PM -0500, Bjorn Andersson wrote:
>>>>>> On Thu, Oct 23, 2025 at 04:06:05PM +0800, yuanjie yang wrote:
>>>>>>> From: Yuanjie Yang <yuanjie.yang@....qualcomm.com>
>>>>>>>
>>>>>>> Build the NT37801 DSI panel driver as module.
>>>>>>>
>>>>>>> Signed-off-by: Yongxing Mou <yongxing.mou@....qualcomm.com>
>>>>>>> Signed-off-by: Yuanjie Yang <yuanjie.yang@....qualcomm.com>
>>>>>>
>>>>>> You (Yuanjie) authored the patch, but forgot to sign-off, then Yongxing
>>>>>> provided certificate of origin, then you provide certificate of origin
>>>>>> and send it to list?
>>>>>>
>>>>>> Please correct.
>>>>>
>>>>> All the display patches were jointly developed by Yongxing and me.
>>>>> So every patch 
>>>>
>>>>
>>>> So two people were working on this absolutely trivial defconfig change?
>>>> I have troubles believing this.
>>> I want to say these patches I am first author and yongxing give me support, so
>>> I think yongxing is second author.
>>>
>>> I want to express my gratitude for Yongxing's support in every patch, so I included
>>> both our names in the sign-off for each one.
>>>
>>> However, if my intention causes any trouble for maintainer, I can remove Yongxing's
>>> sign-off from this patch.
>>
>>
>> Please read submitting patches to understand what Signed-off-by means.
>> Otherwise I have doubts we can accept your patches - you simply do not
>> understand what you are certifying.
> Thanks for your tips, and I learn some tips from submitting patches: 
> https://elixir.bootlin.com/linux/v6.18-rc3/source/Documentation/process/submitting-patches.rst#L524
> 
> I thinks below sign should be true, if you also think it true, I will use it in next patches.
> 
>  Co-developed-by: Yongxing Mou <yongxing.mou@....qualcomm.com>

How does co-developing match what you wrote "give me support"?

>  Signed-off-by: Yongxing Mou <yongxing.mou@....qualcomm.com>
>  Signed-off-by: Yuanjie Yang <yuanjie.yang@....qualcomm.com>



Best regards,
Krzysztof