[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251110124615.4c8203fd@gandalf.local.home>
Date: Mon, 10 Nov 2025 12:46:15 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Christian Brauner <brauner@...nel.org>, 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>, 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 Mon, 10 Nov 2025 19:25:07 +0200
Laurent Pinchart <laurent.pinchart@...asonboard.com> 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.
Agreed. Tooling that performs "mechanical transformations like variable
renaming" is definitely in scope of this document. The number of times I've
seen this "simple" activity make mistakes. It most definitely should be
disclosed if a tool helped in this regard.
Anyway,
Reviewed-by: Steven Rostedt <rostedt@...dmis.org>
-- Steve
Powered by blists - more mailing lists