linux-kernel - Re: [PATCH v2 1/5] RAS: Report all ARM processor CPER information to userspace

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] [day] [month] [year] [list]

Message-ID: <20240902090434.GAZtV_ooWloe-TYzO1@fat_crate.local>
Date: Mon, 2 Sep 2024 11:04:34 +0200
From: Borislav Petkov <bp@...en8.de>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Tony Luck <tony.luck@...el.com>,
	Daniel Ferguson <danielf@...amperecomputing.com>,
	Ard Biesheuvel <ardb@...nel.org>, James Morse <james.morse@....com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Len Brown <lenb@...nel.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Shiju Jose <shiju.jose@...wei.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Dave Jiang <dave.jiang@...el.com>, Ira Weiny <ira.weiny@...el.com>,
	Shuai Xue <xueshuai@...ux.alibaba.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Tyler Baicar <tbaicar@...eaurora.org>,
	Will Deacon <will@...nel.org>, Xie XiuQi <xiexiuqi@...wei.com>,
	linux-acpi@...r.kernel.org, linux-edac@...r.kernel.org,
	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Shengwei Luo <luoshengwei@...wei.com>,
	Jason Tian <jason@...amperecomputing.com>, m.chehab@...wei.com
Subject: Re: [PATCH v2 1/5] RAS: Report all ARM processor CPER information to
 userspace

On Mon, Sep 02, 2024 at 06:12:36AM +0200, Mauro Carvalho Chehab wrote:
> Ok. Will address those at the hole series, sending you later today
> a new version. Except for those, are patches 2-5 ok?

Haven't looked at them yet.

> Usually, I don't use "this patch". In this specific case, I wanted
> to bold the new fields that were added to the ARM trace event, making
> clear that before the changeset, none of such fields exist; they were
> added on such change. On other words, the keyword here is not patch,
> but instead "After". Maybe I can replace it with "now", e. g.:

Yes, and you can see what you're doing in the patch itself.

> Anyway, it sounds that the custody chan can better be written as:
> 
> 	Co-authored-by: Jason Tian <jason@...amperecomputing.com>
> 	Co-authored-by: Signed-off-by: Shengwei Luo <luoshengwei@...wei.com>
> 	Co-authored-by: Daniel Ferguson <danielf@...amperecomputing.com>  
> 	Signed-off-by: Jason Tian <jason@...amperecomputing.com>
> 	Signed-off-by: Shengwei Luo <luoshengwei@...wei.com>
> 	Signed-off-by: Daniel Ferguson <danielf@...amperecomputing.com>  

The tag's name is Co-developed-by: and yes, I think it makes more sense here.

Note:

"Since Co-developed-by: denotes authorship, every Co-developed-by: must be
immediately followed by a Signed-off-by: of the associated co-author.
Standard sign-off procedure applies, i.e. the ordering of Signed-off-by: tags
should reflect the chronological history of the patch insofar as possible,
regardless of whether the author is attributed via From: or Co-developed-by:.
Notably, the last Signed-off-by: must always be that of the developer
submitting the patch."

It is all documented:

Documentation/process/submitting-patches.rst

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette