From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1163512AbdKRKHw (ORCPT <rfc822;w@1wt.eu>);
        Sat, 18 Nov 2017 05:07:52 -0500
Received: from mail-wm0-f65.google.com ([74.125.82.65]:46430 "EHLO
        mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1163499AbdKRKHq (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 18 Nov 2017 05:07:46 -0500
X-Google-Smtp-Source: AGs4zMaz6VFjq0VtjpygjI8/FqvARtX8Tjbvn9fy/IpjONBYLP/2NeLX2U1NBe8jiQX//j4izdCzWQ==
Message-ID: <1510999663.4806.28.camel@elementarea.net>
Subject: Re: [PATCH] checkpatch: allow URL >80 chars
From: Andreas Brauchli <a.brauchli@elementarea.net>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org
Date: Sat, 18 Nov 2017 11:07:43 +0100
In-Reply-To: <1510982478.31022.3.camel@perches.com>
References: <1510934219.2407.4.camel@elementarea.net>
         <1510982478.31022.3.camel@perches.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.1-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fre, 2017-11-17 at 21:21 -0800, Joe Perches wrote:
> On Fri, 2017-11-17 at 16:56 +0100, Andreas Brauchli wrote:
> > Allow URL to exceed the 80 char limit for improved interaction in
> > adaption to ongoing but undocumented practice.
> > 
> > $ git grep -E '://\S{77}.*' -- '*.[ch]'
> > 
> > The patch checks that the URL is indeed on its own line in that it
> > allows a maximal prefix of 4 characters to account for a URL after a
> > comment (e.g. ' // https://...')
> > 
> > The URL format allows for up to 5 protocol characters before the
> > separator :// (e.g. https, git, ...). Additionally, an URL starting
> > with a "domain.tld" or "subdomain.domain" pattern (e.g.
> > 'www.kernel.org') is also accepted.
> > 
> > $rawline is used in the check as comments are removed from $line.
> > 
> > Signed-off-by: Andreas Brauchli <andreas.brauchli@sensirion.com>
> > ---
> >  scripts/checkpatch.pl | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 8b80bac055e4..aed447923354 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -2904,6 +2904,11 @@ sub process {
> >  			} elsif ($line =~ /^\+.*\bEFI_GUID\s*\(/) {
> >  				$msg_type = "";
> >  
> > +			# URL (w/ minimal padding e.g. "+ // ")
> > +			} elsif ($rawline =~ /^\+.*?\b((?:\w{1,5}:\/\/|\w+\.\w+)\S+).*$/ &&
> 
> nack.
> 
> this matches member dereference lines like
> 
> 	foo.bar = baz;
> 
> and include lines like
> 
> 	#include <foo.h>

Agreed, there are even a few false positives (all member derefs).
Apologies for failing to catch those.

Is the patch acceptable if it only catches URL with protocol specifiers
foo:// ? That would catch most cases and doesn't show false positives:
$ git grep -E '://\S{75}.*' -- '*.[ch]'

Cheers,
Andreas