Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <dddb87a6ffb94b6b8046eb2eca1480a7ca37f962.camel@perches.com>
Subject: Re: [PATCH RESEND] checkpatch: Do not check git commit description
 style when backport the upstream commit
From:   Joe Perches <joe@perches.com>
To:     Tiezhu Yang <yangtiezhu@loongson.cn>,
        Andrew Morton <akpm@linux-foundation.org>,
        Andy Whitcroft <apw@canonical.com>
Cc:     linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>
Date:   Tue, 24 Nov 2020 19:51:48 -0800
In-Reply-To: <1606275347-19297-1-git-send-email-yangtiezhu@loongson.cn>
References: <1606275347-19297-1-git-send-email-yangtiezhu@loongson.cn>
Content-Type: text/plain; charset="ISO-8859-1"
User-Agent: Evolution 3.38.1-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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?