Ignacio Peña <ignacio.pena87@xxxxxxxxx> writes: > From: Ignacio Pena <ignacio.pena87@xxxxxxxxx> > > Add documentation for patch-validator, a comprehensive tool that helps > kernel contributors validate their patches before submission. This tool > catches common mistakes that frequently lead to patch rejections, > improving the quality of submissions and reducing maintainer workload. > > The validator performs 21+ automated checks including: > - Patch format validation (subject line, changelog placement) > - DCO compliance and licensing verification > - checkpatch.pl integration with enhanced reporting > - Build impact analysis and testing recommendations > - Common novice pattern detection > - Git configuration validation > > Also includes companion tools for finding first contributions, > testing patches safely, and validating patch series. > > Link: https://github.com/ipenas-cl/kernel-patch-validator > Signed-off-by: Ignacio Pena <ignacio.pena87@xxxxxxxxx> > --- > Documentation/dev-tools/index.rst | 1 + > Documentation/dev-tools/patch-validator.rst | 287 +++++++++++++++++++ > 2 files changed, 288 insertions(+) > create mode 100644 Documentation/dev-tools/patch-validator.rst Interesting ... overall, we don't generally have detailed documentation for out-of-tree utilities, though there isn't necessarily any reason why we couldn't. But I'm curious as to why you haven't submitted the tool itself? Thanks, jon
