All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Geyslan G. Bem" <geyslan@gmail.com>,
	Robo Bot <apw@canonical.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Peter Senna Tschudin <peter.senna@gmail.com>
Subject: Re: [BUG] checkpatch: unescaped left brace in regex is deprecated
Date: Mon, 07 Dec 2015 15:06:26 -0800	[thread overview]
Message-ID: <1449529586.7162.10.camel@perches.com> (raw)
In-Reply-To: <CAGG-pURfU4kQBCS8W4no5SinhWVPyNVv8MamWYCy_rN00QJkxg@mail.gmail.com>

On Mon, 2015-12-07 at 19:53 -0300, Geyslan G. Bem wrote:
> Hello,

hello.

> Follow checkpatch output using perl 5.22.0.
> 
> geyslan@hb ~/Projects/linux $ scripts/checkpatch.pl -f
> drivers/usb/host/ehci-hub.c
> Unescaped left brace in regex is deprecated, passed through in regex;
> marked by <-- HERE in m/\((?^x:
> 

No HERE here.  Are you using linux-next?

There have been patches applied for this warning already.

see:

commit 4e5d56bdf892e18832a6540b63ebf709966bce2a
Author: Eddie Kovsky <ewk@edkovsky.org>
Date:   Wed Sep 9 15:37:52 2015 -0700

    checkpatch: fix left brace warning
    
    Using checkpatch.pl with Perl 5.22.0 generates the following warning:
    
        Unescaped left brace in regex is deprecated, passed through in regex;
 5.

  reply	other threads:[~2015-12-07 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 22:53 [BUG] checkpatch: unescaped left brace in regex is deprecated Geyslan G. Bem
2015-12-07 23:06 ` Joe Perches [this message]
2015-12-07 23:36   ` Geyslan G. Bem
     [not found]     ` <CAGG-pUQsUnAx2rTTgoX4WhUHNGo3R=9siqAVhaOsqB=P9eqnSg@mail.gmail.com>
2015-12-10 11:24       ` Geyslan G. Bem
2015-12-15 23:58         ` Geyslan G. Bem
2015-12-16  0:13           ` Joe Perches
2015-12-16 11:21             ` Geyslan G. Bem
2015-12-30 15:52               ` Geyslan G. Bem

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1449529586.7162.10.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=geyslan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.