From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Kees Cook <kees@kernel.org>
Cc: Dan Carpenter <error27@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefano Zacchiroli <zack@upsilon.cc>,
Steven Rostedt <rostedt@goodmis.org>,
Laura Abbott <labbott@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Wenwen Wang <wenwen@cs.uga.edu>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hardening@vger.kernel.org,
Dawei Feng <dawei.feng@seu.edu.cn>
Subject: Re: [PATCH v3] Documentation/process: Add Researcher Guidelines
Date: Tue, 16 Jun 2026 10:09:39 +0300 [thread overview]
Message-ID: <ajD2s5Q0sP679Mbh@ashevche-desk.local> (raw)
In-Reply-To: <202606151547.DB4095584@keescook>
On Mon, Jun 15, 2026 at 03:48:02PM -0700, Kees Cook wrote:
> On Mon, Jun 15, 2026 at 03:48:22PM +0200, Andy Shevchenko wrote:
> > On Thu, May 28, 2026 at 01:34:34PM +0300, Dan Carpenter wrote:
> > > On Fri, Mar 04, 2022 at 10:14:18AM -0800, Kees Cook wrote:
...
> > > > + x86_64 and arm64 defconfig builds with CONFIG_FOO_BAR=y using GCC
> > > > + 11.2 show no new warnings, and LeakMagic no longer warns about this
> > > > + code path. As we don't have a FooBar device to test with, no runtime
> > > > + testing was able to be performed.
> > >
> > > People have started sending commit messages in this exact template and
> > > normally I would ask them resend with the meta commentary from this
> > > paragraph below the --- cut off line.
> > >
> > > Do we really want this "Compile tested only" stuff in the permanent git
> > > log?
> >
> > +1 here, can we rather avoid flooding commit messages with the meta, that
> > anyways is available in lore.kernel.org archives?
>
> Hm, I have gotten a lot of push-back from maintainers (reasonablly)
> wanting to know the specific level of testing patches get. In the case
> of lacking hardware, this seems like useful information still.
I am *not* against providing this information (actually I on the same page),
I'm just against putting it into the commit message! We have a comment block
put it there, please.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-06-16 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 18:14 [PATCH v3] Documentation/process: Add Researcher Guidelines Kees Cook
2022-03-09 23:20 ` Jonathan Corbet
2026-05-28 10:34 ` Dan Carpenter
2026-06-15 13:48 ` Andy Shevchenko
2026-06-15 14:58 ` Jonathan Corbet
2026-06-15 15:02 ` Andy Shevchenko
2026-06-15 22:48 ` Kees Cook
2026-06-16 7:09 ` Andy Shevchenko [this message]
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=ajD2s5Q0sP679Mbh@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=corbet@lwn.net \
--cc=dawei.feng@seu.edu.cn \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=kees@kernel.org \
--cc=labbott@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rostedt@goodmis.org \
--cc=wenwen@cs.uga.edu \
--cc=zack@upsilon.cc \
/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