linux-kernel - Re: [PATCH v3 2/9] dt-bindings: display: add verisilicon,dc

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: <f944f0b28f62233b1874e0f00c0a130d71845417.camel@icenowy.me>
Date: Mon, 24 Nov 2025 19:13:08 +0800
From: Icenowy Zheng <uwu@...nowy.me>
To: Krzysztof Kozlowski <krzk@...nel.org>, Maarten Lankhorst
 <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>, 
 Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
 Simona Vetter <simona@...ll.ch>, Rob Herring <robh@...nel.org>, Krzysztof
 Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Drew
 Fustini <fustini@...nel.org>, Guo Ren <guoren@...nel.org>, Fu Wei
 <wefu@...hat.com>, Philipp Zabel <p.zabel@...gutronix.de>, Heiko Stuebner
 <heiko@...ech.de>, Andrzej Hajda <andrzej.hajda@...el.com>, Neil Armstrong
 <neil.armstrong@...aro.org>,  Robert Foss <rfoss@...nel.org>, Laurent
 Pinchart <Laurent.pinchart@...asonboard.com>, Jonas Karlman
 <jonas@...boo.se>, Jernej Skrabec <jernej.skrabec@...il.com>, Michal
 Wilczynski <m.wilczynski@...sung.com>
Cc: Han Gao <rabenda.cn@...il.com>, Yao Zi <ziyao@...root.org>, 
	dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v3 2/9] dt-bindings: display: add verisilicon,dc

在 2025-11-24星期一的 12:09 +0100，Krzysztof Kozlowski写道：
> On 24/11/2025 12:04, Icenowy Zheng wrote:
> > 在 2025-11-24星期一的 12:01 +0100，Krzysztof Kozlowski写道：
> > > On 24/11/2025 11:52, Icenowy Zheng wrote:
> > > > Verisilicon has a series of display controllers prefixed with
> > > > DC
> > > > and
> > > > with self-identification facility like their GC series GPUs.
> > > > 
> > > > Add a device tree binding for it.
> > > > 
> > > > Depends on the specific DC model, it can have either one or two
> > > > display
> > > > outputs, and each display output could be set to DPI signal or
> > > > "DP"
> > > > signal (which seems to be some plain parallel bus to HDMI
> > > > controllers).
> > > > > Signed-off-by: Icenowy Zheng <uwu@...nowy.me>
> > > > Signed-off-by: Icenowy Zheng <zhengxingda@...as.ac.cn>
> > > 
> > > Wrong DCO chain order. You send it as icenowy.me, so this must be
> > > last
> > > SoB. This identity is the last one certifying DCO. Please kindly
> > > read
> > > submitting patches, so you know what you are certifying here.
> > 
> > Well I mapped the @iscas.ac.cn mail to the @icenowy.me one in the
> > last
> > patch.
> > 
> > Or maybe I should make it the first patch?
> 
> .mailmap has effect on b4 and git send-email, so maybe that's the
> answer. The problem is that:
> 1. This email has sender address @icenowy.me
> 2. It's SoB is not the last one.

Well, I think a patch that is already sent shouldn't have the From
field changing when bumping revision, and a patch modified by one
identity should have the modifying one's SoB added.

So here I am using the @icenowy.me mail (which can represent the
@iscas.ac.cn mail according to the mailmap) to send the patch that is
processed by @iscas.ac.cn mail.

Sending the patch with @iscas.ac.cn mail needs some extra setup
(because of some weird security requirement).

> 
> This needs to be fixed. The order of patches for me does not matter,
> I
> don't think it would fix the issue here either.
> 
> Anyway, please trim your responses, so I will not have to scroll
> through
> lines of code to find that you did not respond there.
> 
> 
> 
> Best regards,
> Krzysztof