linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Tatschner <stefan@sevenbyte.org>
To: linux-kernel@vger.kernel.org
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] checkpatch: Fix perl 5.22 brace deprecation warnings
Date: Fri, 04 Sep 2015 10:10:33 +0200	[thread overview]
Message-ID: <1441354233.24275.3.camel@sevenbyte.org> (raw)
In-Reply-To: <1436383335-2674-1-git-send-email-stefan@sevenbyte.org>

On Mi, 2015-07-08 at 21:22 +0200, Stefan Tatschner wrote:
> This patch fixes four "Unescaped left brace in regex is
> deprecated" (perl 5.22) warnings by escaping left braces
> properly.
> 
> Signed-off-by: Stefan Tatschner <stefan@sevenbyte.org>

Are there any updates on this patch? It seems it got lost in the noise.
It fixes these deprecation warnings on perl 5.22.0:

Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\#\s*define.*do\s{ <-- HERE / at scripts/checkpatch.pl line 3523.
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\(.*\){ <-- HERE / at scripts/checkpatch.pl line 4035.
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/do{ <-- HERE / at scripts/checkpatch.pl line 4036.
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^\({ <-- HERE / at scripts/checkpatch.pl line 4483.

Stefan

      reply	other threads:[~2015-09-04  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 19:22 [PATCH] checkpatch: Fix perl 5.22 brace deprecation warnings Stefan Tatschner
2015-09-04  8:10 ` Stefan Tatschner [this message]

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=1441354233.24275.3.camel@sevenbyte.org \
    --to=stefan@sevenbyte.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).