linux-kernel - Re: [PATCH RESEND] checkpatch: Do not check git commit description style when backport the upstream commit

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: <995e0acb-c219-ea00-f078-7582516e25de@loongson.cn>
Date:   Wed, 25 Nov 2020 12:08:04 +0800
From:   Tiezhu Yang <yangtiezhu@...ngson.cn>
To:     Joe Perches <joe@...ches.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Andy Whitcroft <apw@...onical.com>
Cc:     linux-kernel@...r.kernel.org, Xuefeng Li <lixuefeng@...ngson.cn>
Subject: Re: [PATCH RESEND] checkpatch: Do not check git commit description
 style when backport the upstream commit

On 11/25/2020 11:51 AM, Joe Perches wrote:
> On Wed, 2020-11-25 at 11:35 +0800, Tiezhu Yang wrote:
>> When backport the upstream commit to the internal LTS kernel version,
>> we usually use the following description [1] [2]:
>>
>> [ Upstream commit cc6528bc9a0c901c83b8220a2e2617f3354d6dd9 ]
>> or
>> commit c51f8f88d705e06bd696d7510aff22b33eb8e638 upstream.
> Internal to what?
>
> If it's your own internal build system, I think you should
> keep your own local patch to checkpatch.
>
> I don't see why the kernel version should accept it.
>
> Is this style used by anyone else?

AFAIK, this style is only used in the stable tree, for example:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.9.y&id=c68a9ca7ca33f1020cca97e4e935c2154bec37c7