ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	dave@sr71.net, Shuah Khan <shuah@kernel.org>,
	Kees Cook <kees@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Miguel Ojeda <ojeda@kernel.org>, NeilBrown <neilb@ownmail.net>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Vlastimil Babka <vbabka@suse.cz>,
	workflows@vger.kernel.org, ksummit@lists.linux.dev
Subject: Re: [PATCH] [v3] Documentation: Provide guidelines for tool-generated content
Date: Sun, 16 Nov 2025 11:01:46 -0500	[thread overview]
Message-ID: <20251116110146.3417edce@batman.local.home> (raw)
In-Reply-To: <2804290.mvXUDI8C0e@rafael.j.wysocki>

On Sun, 16 Nov 2025 13:38:35 +0100
"Rafael J. Wysocki" <rafael@kernel.org> wrote:

> On Sunday, November 16, 2025 12:30:27 AM CET Thomas Gleixner wrote:
> > On Sat, Nov 15 2025 at 14:07, Steven Rostedt wrote:  
> > > On Sat, 15 Nov 2025 14:05:56 -0500
> > > Steven Rostedt <rostedt@goodmis.org> wrote:
> > >  
> > >> As Dave responded to Luis, although that is a good idea, it's out of
> > >> scope for this document (for now).  
> > >
> > > I should have said it's out of scope for this patch, not document. The
> > > point is that what tag to use for this is a separate discussion.  
> > 
> > Which should be held in the context of this patch to make it complete.  
> 
> I agree, it would be good to get it all done in one go.
> 
> 

It's still out of scope of this patch. As the change log states:

    Note, though, there are fundamentally no new or unique rules in this
    new document. It clarifies expectations that the kernel community has
    had for many years.

A tag is a new rule. This document is to express existing behavior.
Adding a tag that currently doesn't match existing behavior should be a
separate patch.

-- Steve

  parent reply	other threads:[~2025-11-16 16:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 18:35 Dave Hansen
2025-11-14 20:08 ` Luis Chamberlain
2025-11-14 22:52   ` Dave Hansen
2025-11-14 20:17 ` SeongJae Park
2025-11-14 22:53   ` Dave Hansen
2025-11-14 23:19 ` dan.j.williams
2025-11-15 15:22 ` Thomas Gleixner
2025-11-15 19:05   ` Steven Rostedt
2025-11-15 19:07     ` Steven Rostedt
2025-11-15 23:30       ` Thomas Gleixner
2025-11-16 12:38         ` Rafael J. Wysocki
2025-11-16 15:25           ` Kees Cook
2025-11-16 16:17             ` Steven Rostedt
2025-11-16 16:01           ` Steven Rostedt [this message]
2025-11-17 19:13         ` Dave Hansen
2025-11-15 19:02 ` Steven Rostedt
2025-11-15 20:10 ` Randy Dunlap

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=20251116110146.3417edce@batman.local.home \
    --to=rostedt@goodmis.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kees@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=neilb@ownmail.net \
    --cc=ojeda@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    --cc=vbabka@suse.cz \
    --cc=workflows@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox