[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9eb9f19-9b77-4ece-ac54-9e25a801c565@sr71.net>
Date: Mon, 10 Nov 2025 09:41:54 -0800
From: Dave Hansen <dave@...1.net>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Christian Brauner <brauner@...nel.org>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Vlastimil Babka <vbabka@...e.cz>, linux-kernel@...r.kernel.org,
"workflows@...r.kernel.org" <workflows@...r.kernel.org>,
"ksummit@...ts.linux.dev" <ksummit@...ts.linux.dev>,
Steven Rostedt <rostedt@...dmis.org>, Dan Williams
<dan.j.williams@...el.com>, Theodore Ts'o <tytso@....edu>,
Sasha Levin <sashal@...nel.org>, Jonathan Corbet <corbet@....net>,
Kees Cook <kees@...nel.org>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Miguel Ojeda <ojeda@...nel.org>,
Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH] [v2] Documentation: Provide guidelines for tool-generated
content
On 11/10/25 09:25, Laurent Pinchart wrote:
>>>> + - Purely mechanical transformations like variable renaming
> Mechanical transformations are often performed with Coccinelle. Given
> how you mention that tool below, I wouldn't frame it as out of scope
> here.
The key here isn't which tool is used, it's how it's used.
If you go use Coccinelle for pure variable renaming, you don't need to
mention it. Same as if you use perl or vim to do a s/foo/bar/.
That said, if you choose to attach your trivial variable renaming
Coccinelle script, everyone will be better off for it.
Powered by blists - more mailing lists