Dave Hansen wrote: > In the last few years, the capabilities of coding tools have exploded. > As those capabilities have expanded, contributors and maintainers have > more and more questions about how and when to apply those > capabilities. > > Add new Documentation to guide contributors on how to best use kernel > development tools, new and old. > > 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. For example, researchers are already asked to > disclose the tools they use to find issues in > Documentation/process/researcher-guidelines.rst. This new document > just reiterates existing best practices for development tooling. > > In short: Please show your work and make sure your contribution is > easy to review. > > Signed-off-by: Dave Hansen <[email protected]> > Reviewed-by: Shuah Khan <[email protected]> > Reviewed-by: Kees Cook <[email protected]> > Reviewed-by: Greg Kroah-Hartman <[email protected]> > Reviewed-by: Miguel Ojeda <[email protected]> > Cc: NeilBrown <[email protected]> > Cc: Lorenzo Stoakes <[email protected]> > Cc: Dan Williams <[email protected]>
All my concerns have been addressed. Reviewed-by: Dan Williams <[email protected]>
