From: Jonathan Corbet <corbet@lwn.net>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Dan Williams <dan.j.williams@intel.com>,
Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
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: Mon, 10 Nov 2025 08:44:09 -0700 [thread overview]
Message-ID: <878qgdzyd2.fsf@trenco.lwn.net> (raw)
In-Reply-To: <414139b0-92bb-4516-8286-732f2d5e6bda@lucifer.local>
Lorenzo Stoakes <lorenzo.stoakes@oracle.com> writes:
> On Mon, Nov 10, 2025 at 08:19:24AM -0700, Jonathan Corbet wrote:
>> Lorenzo Stoakes <lorenzo.stoakes@oracle.com> writes:
>>
>> > It also seems slightly odd to produce this in advance of the maintainer's
>> > summit, as I felt there was some agreement that the topic should be discussed
>> > there?
>> >
>> > Obviously there may be very good reasons for this but it'd be good for
>> > them to be clarified and those who engaged in these discussions to be
>> > cc'd also (or at least ping on threads linking!)
>>
>> The reasoning, from my point of view at least, was to have a starting
>> point for the Maintainers Summit discussion. Trying to start from
>> scratch in Tokyo seems unlikely to get us far.
>
> I Would understand if this was an RFC or there was a big block saying 'this
> is not yet official' or something, but lt the moment it seems like a change
> sent only to the TAB committee as an apparent 'fait complete' with no
> indication of it being just a starting point? (forgive me if I missed it).
>
> I think pinging the relevant threads would have been helpful, but maybe we
> need a better procedure in general for this kind of thing.
I agree that sending to those threads would have made sense. Folks are
busy ... I didn't think of that, and it only occurred to me this weekend
that I knew a certain web site where it might make sense to post a
note...
> I'm not invited to the MS but I wondered if this planned to be discussed
> there? I don't really care about my involvement, only that there is
> community engagement on this.
The agenda has not been worked out, but this topic seems certain to be
there once it is.
jon
next prev parent reply other threads:[~2025-11-10 15:44 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
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 [this message]
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=878qgdzyd2.fsf@trenco.lwn.net \
--to=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=lorenzo.stoakes@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox