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: <a8089e458bdf6fbad45cd6be838b4cf75396918f.camel@icenowy.me>
Date: Mon, 24 Nov 2025 23:25:01 +0800
From: Icenowy Zheng <uwu@...nowy.me>
To: Krzysztof Kozlowski <krzk@...nel.org>, Conor Dooley <conor@...nel.org>
Cc: 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>, 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星期一的 13:31 +0100,Krzysztof Kozlowski写道:
> On 24/11/2025 13:20, Conor Dooley wrote:
> > On Mon, Nov 24, 2025 at 01:08:00PM +0100, Krzysztof Kozlowski
> > wrote:
> > > On 24/11/2025 13:05, Conor Dooley wrote:
> > > > 
> > > > I don't really get what the fuss is with the dual signoff,
> > > > what's the
> > > > point having both when they represent the same person? Pretty
> > > > sure it
> > > > was you (Krzysztof) and Arnd that told me not to both doing the
> > > > double
> > > > signoff.
> > > 
> > > I do not object having or not having dual signed off HERE.
> > > 
> > > I never said that. Just like I never said "From" has to be
> > > changed.
> > 
> > I didn't say you objected to both being there. *I* am saying that
> > it is
> 
> Ah, sure. Yes, if both identities work I would propose to skip second
> SoB. But I also stopped objecting of having two identities listed, as
> long as they are correct.

Well it's unfortunate that some policy now requires me to list the
second identity.

Should I resend the whole patchset with the ISCAS mail?

(The problem with it is that it forces application-specific password,
and with git-send-email lacking a proper key store, this makes the
password a one-time one.)

> 
> > probably not worth doing. That's especially the case when it is
> > adding
> > complication about correct ordering of signoffs and maybe
> > interacting with
> > how git-send-email decides to insert From: fields.
> > 
> 
> 
> 
> Best regards,
> Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ