All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Kees Cook <kees@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Miguel Ojeda <ojeda@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] [v2] Documentation: Provide guidelines for tool-generated content
Date: Fri, 7 Nov 2025 17:58:23 +0700	[thread overview]
Message-ID: <aQ3Qz4QuUX1S2her@archie.me> (raw)
In-Reply-To: <20251105231514.3167738-1-dave.hansen@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

On Wed, Nov 05, 2025 at 03:15:14PM -0800, Dave Hansen wrote:
> +Out of Scope
> +============
> +
> +These guidelines do not apply to tools that make trivial tweaks to
> +preexisting content. Nor do they pertain to AI tooling that helps with
> +menial tasks. Some examples:
> +
> + - Spelling and grammar fix ups, like rephrasing to imperative voice
> + - Typing aids like identifier completion, common boilerplate or
> +   trivial pattern completion
> + - Purely mechanical transformations like variable renaming
> + - Reformatting, like running Lindent, ``clang-format`` or
> +   ``rust-fmt``

Manually fixing checkpatch warnings is also out-of-scope?

Confused... 

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2025-11-07 10:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 23:15 [PATCH] [v2] Documentation: Provide guidelines for tool-generated content Dave Hansen
2025-11-06 22:42 ` Shuah
2025-11-06 22:49   ` Dave Hansen
2025-11-07  3:40 ` Kees Cook
2025-11-07  8:47 ` Greg Kroah-Hartman
2025-11-07 10:58 ` Bagas Sanjaya [this message]
2025-11-08  0:11 ` dan.j.williams
2025-11-13 22:17   ` Dave Hansen
2025-11-08  1:52 ` Miguel Ojeda
2025-11-13 22:21   ` Dave Hansen
2025-11-10  7:43 ` Vlastimil Babka
2025-11-10  8:58   ` Christian Brauner
2025-11-10 16:08     ` Dave Hansen
2025-11-10 17:25     ` Laurent Pinchart
2025-11-10 17:41       ` Dave Hansen
2025-11-10 17:44       ` Linus Torvalds
2025-11-10 17:56         ` Luck, Tony
2025-11-10 18:39         ` Mike Rapoport
2025-11-10 19:05           ` Linus Torvalds
2025-11-10 19:18             ` H. Peter Anvin
2025-11-10 19:36               ` Linus Torvalds
2025-11-10 19:54                 ` Steven Rostedt
2025-11-10 20:00                   ` Konstantin Ryabitsev
2025-11-10 20:25                     ` Steven Rostedt
2025-11-10 21:21                   ` James Bottomley
2025-11-10 21:42                     ` Steven Rostedt
2025-11-10 21:52                       ` Luck, Tony
2025-11-10 22:07                         ` James Bottomley
2025-11-10 23:16                   ` Theodore Ts'o
2025-11-11  9:35                 ` Lorenzo Stoakes
2025-11-11 13:08                   ` Theodore Ts'o
2025-11-10 17:46       ` Steven Rostedt
2025-11-10 10:48 ` Lorenzo Stoakes
2025-11-10 11:15   ` Lorenzo Stoakes
2025-11-10 15:19   ` Jonathan Corbet
2025-11-10 15:30     ` Lorenzo Stoakes
2025-11-10 15:44       ` Jonathan Corbet
2025-11-10 16:35   ` Dave Hansen
2025-11-10 16:51     ` Lorenzo Stoakes
2025-11-10 18:29   ` Steven Rostedt
2025-11-11 23:45 ` NeilBrown
2025-11-14  1:09   ` Dave Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aQ3Qz4QuUX1S2her@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.