Aaron Conole <[email protected]> writes: > This series cleans up and clarifies certain issues in the checkpatch > infrastructure. Additionally, a fix for the some of the matches is included. > > The two features added by this series are: > 1. The ability to parse a non-patch file (useful for applying cleanups to > existing code) > 2. Printing the line number where a change occurs in the file, instead of > in the patchfile. > > With these two features, a simple script > for check_file in lib/*.c; do ./utilities/checkpatch.py -f $check_file; > done > > will print a number of violations (hopefully, correctly!). > > Aaron Conole (7): > checkpatch: Announce the file where errors occur > checkpatch: Print the line in question distinctly > checkpatch: convert some of the warnings > checkpatch: Print file line numbers > checkpatch: Fix signoff error > checkpatch: Add file-parsing mode > checkpatch: fix the if and whitespace checks > > utilities/checkpatch.py | 92 > ++++++++++++++++++++++++++++++++++++++----------- > 1 file changed, 72 insertions(+), 20 deletions(-)
Ping. Is it possible to get this series reviewed? Thanks, -Aaron _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
