linux-kernel - Re: [PATCH 3/3] New script to check coding-style compliance on multiple regular files

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: <20070929101012.GA12555@uranus.ravnborg.org>
Date:	Sat, 29 Sep 2007 12:10:12 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Erez Zadok <ezk@...sunysb.edu>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, apw@...dowen.org,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH 3/3] New script to check coding-style compliance on multiple regular files

Hi Erez.

On Fri, Sep 28, 2007 at 05:32:02PM -0400, Erez Zadok wrote:
> The script calls checkpatch.pl on each file, and formats any error messages
> to comply with standard compiler error messages:
> 
> 	file_name:line_number:error_message
> 
> This is particularly useful when run from within a text editor which can
> parse these error messages and show the user a buffer with the file in
> question, placing the cursor on the offending line (e.g., Emacs's "M-x
> next-error" command, bound by default to C-x `).

The concept is wrong here. If we want checkpatch to generate
message in standard gcc format then we should fix checkpatch and
not add a wrapper script around it.

For checkpatch related patches please forward them to the checkpatch
maintainers.

>From MAINTAINERS:

CHECKPATCH
P:      Andy Whitcroft
M:      apw@...dowen.org
P:      Randy Dunlap
M:      rdunlap@...otime.net
P:      Joel Schopp
M:      jschopp@...tin.ibm.com
S:      Supported



	Sam
-
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/