lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080114173032.GE19327@shadowen.org>
Date:	Mon, 14 Jan 2008 17:30:32 +0000
From:	Andy Whitcroft <apw@...dowen.org>
To:	Paolo Ciarrocchi <paolo.ciarrocchi@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: checkpatch: add filename before the summary line

On Sun, Jan 13, 2008 at 11:34:05PM +0100, Paolo Ciarrocchi wrote:
> With the patch applied the output of checkpatch.pl is as follow:
> ./arch/arm/mach-footbridge/ebsa285-pci.c 
> total: 1 errors, 0 warnings, 48 lines checked
> 
> Adding the file name allowed me to collects stats running:
> 	find . -name *.c |xargs ./scripts/checkpatch.pl --file |grep -B 1 total
> but I though it might me useful for other purposes to add the file name
> after the list of errors and warnings and before the summary,
> when the list is long I find handy to print out the filename as a reminder.

Hmmm, that being unconfitional would probabally break a raft of other
users.  Also would it be more useful to put it on the front of the
summary line?  So that if you have a bunch of files to check then you
get something more like:

foo: total: 1 errors, ...
bar: total: 0 errors, ...

-apw
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ