From: Dave Hansen <dave.hansen@intel.com>
To: Shuah <shuah@kernel.org>,
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>
Subject: Re: [PATCH] [v2] Documentation: Provide guidelines for tool-generated content
Date: Thu, 6 Nov 2025 14:49:52 -0800 [thread overview]
Message-ID: <bff14f9e-d02c-43f3-8c39-8924a5679d53@intel.com> (raw)
In-Reply-To: <c548835c-091b-4714-a0bf-46e50c08f7e6@kernel.org>
On 11/6/25 14:42, Shuah wrote:
...
>> +Detection of a problem is also a part of the development process; if a
>
> It is good to emphasize testing is also part of development.
> How about rephrasing "Detection of a problem and testing the fix for it
> is also part of the development process;"
Both of your suggestions look great to me. Thanks, Shuah!
I'll get them incorporated in the next version.
next prev parent reply other threads:[~2025-11-06 22:49 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 [this message]
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
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=bff14f9e-d02c-43f3-8c39-8924a5679d53@intel.com \
--to=dave.hansen@intel.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.