[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a102bb51a8ebde2e22d9527fb00a2c1f64c6e69f.camel@perches.com>
Date: Tue, 24 Nov 2020 20:24:15 -0800
From: Joe Perches <joe@...ches.com>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Whitcroft <apw@...onical.com>,
Greg KH <gregkh@...uxfoundation.org>,
Sasha Levin <sashal@...nel.org>
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 Wed, 2020-11-25 at 12:08 +0800, Tiezhu Yang wrote:
> 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
Greg?/Sasha?
https://lore.kernel.org/lkml/995e0acb-c219-ea00-f078-7582516e25de@loongson.cn/T/#m2f3d87bd985bf3d4d7b63f1fa4f0490baa01119b
Is this in your scripts?
Is this something you want/use?
Powered by blists - more mailing lists