Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030896AbbDWTxS (ORCPT ); Thu, 23 Apr 2015 15:53:18 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:35900 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030582AbbDWTxQ (ORCPT ); Thu, 23 Apr 2015 15:53:16 -0400 Message-ID: <55394DA8.3060705@gmail.com> Date: Thu, 23 Apr 2015 21:53:12 +0200 From: Mateusz Kulikowski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Joe Perches CC: apw@canonical.com, davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/2] checkpatch: suggest using eth_zero_addr() and eth_broadcast_addr() References: <1429481816-6664-1-git-send-email-mateusz.kulikowski@gmail.com> <1429481816-6664-3-git-send-email-mateusz.kulikowski@gmail.com> <1429492384.27863.13.camel@perches.com> <5536B9D2.7030200@gmail.com> <1429651348.31675.12.camel@perches.com> <5536C4C2.4000001@gmail.com> <1429655247.31675.20.camel@perches.com> In-Reply-To: <1429655247.31675.20.camel@perches.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2004 Lines: 83 On 22.04.2015 00:27, Joe Perches wrote: > On Tue, 2015-04-21 at 23:44 +0200, Mateusz Kulikowski wrote: >> On 21.04.2015 23:22, Joe Perches wrote: >>> On Tue, 2015-04-21 at 22:57 +0200, Mateusz Kulikowski wrote: >> (...) (...) >> True, True; If you prefer $line and ability to --fix - I'll use that in v3 > > I suppose you could do both $line and $stat > and the fix would only work when it's on a > single line. > > Perhaps something like this would work: > > if ($line =~ /whatever/ || > (defined($stat) && $stat =~ /whatever/)) { > if (WARN(...) && > $fix) { > fixed[$fixlinenr] =~ s/whatever/appropriate/; > } > } Isn't it enough to just match $stat and do fix for line (that in some cases will just not match)? One more thing I noticed funny behavior about $stat matches - it reports the same error several times (including as "scope" whole file) Is it feature or "feature" or I missed something? Ex. file: -------------- cut int foo(void) { baz(); memset(a, b, 0); bar(); } -------------- cut Output of (@master) -------------- cut $ scripts/checkpatch.pl -f test42.c --types MEMSET ERROR: memset to 0's uses 0 as the 2nd argument, not the 3rd #1: FILE: test42.c:1: +int foo(void) { baz(); memset(a, b, 0); bar(); } ERROR: memset to 0's uses 0 as the 2nd argument, not the 3rd #2: FILE: test42.c:2: +{ baz(); memset(a, b, 0); bar(); } ERROR: memset to 0's uses 0 as the 2nd argument, not the 3rd #4: FILE: test42.c:4: +memset(a, b, 0); total: 3 errors, 0 warnings, 6 lines checked NOTE: Used message types: MEMSET test42.c has style problems, please review. If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. --------------cut Regards, Mateusz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/