From: "Arend van Spriel" <arend@broadcom.com>
To: "Andy Whitcroft" <apw@canonical.com>,
"Joe Perches" <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: checkpatch bailing out
Date: Sat, 2 Mar 2013 13:02:40 +0100 [thread overview]
Message-ID: <5131EA60.40607@broadcom.com> (raw)
With my laptop being broken I have to work on a server provided by my
employer and I am preparing some patches for submission. So I intended
to run checkpatch, but I get the following message after which the
script bails out:
$ git format-patch -1 --stdout | scripts/checkpatch.pl -
Nested quantifiers in regex; marked by <-- HERE in m/(\((?:[^\(\)]++ <--
HERE |(?-1))*\))/ at scripts/checkpatch.pl line 347.
The server runs RHEL5
2.6.18-308.20.1.el5 #1 SMP x86_64 GNU/Linux
Perl interpreter:
$ /usr/bin/perl -v
This is perl, v5.8.8 built for x86_64-linux-thread-multi
My repository is based on wireless-testing repo.
Did a quick search on LKML, but not finding anything like this. Any help
would be appreciated here.
Gr. AvS
next reply other threads:[~2013-03-02 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 12:02 Arend van Spriel [this message]
2013-03-02 13:07 ` checkpatch bailing out Joe Perches
2013-03-02 13:26 ` Arend van Spriel
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=5131EA60.40607@broadcom.com \
--to=arend@broadcom.com \
--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