Re: [PATCH v3] Documentation/process: Add Researcher Guidelines

[Kees Cook]

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.

-- 
Kees Cook