From: Stephen Rothwell <sfr@canb.auug.org.au>
To: john.hubbard@gmail.com
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Ofir Drang <ofir.drang@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] checkpatch: revert broken NOTIFIER_HEAD check
Date: Mon, 12 Aug 2019 11:30:36 +1000 [thread overview]
Message-ID: <20190812113036.7a5dd650@canb.auug.org.au> (raw)
In-Reply-To: <20190811225443.31161-2-jhubbard@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
Hi John,
On Sun, 11 Aug 2019 15:54:43 -0700 john.hubbard@gmail.com wrote:
>
> From: John Hubbard <jhubbard@nvidia.com>
>
> commit 1a47005dd5aa ("checkpatch: add *_NOTIFIER_HEAD as var
> definition") causes the following warning when run on some
> patches:
>
> Unescaped left brace in regex is passed through in regex;
> marked by < --HERE in m/(?:
> ...
> [238 lines of appalling perl output, mercifully not included]
> ...
> )/ at ./scripts/checkpatch.pl line 3889.
>
> This is broken, so revert it until a better solution is found.
>
> Fixes: 1a47005dd5aa ("checkpatch: add *_NOTIFIER_HEAD as var
> definition")
Thanks for the report.
I have removed that patch from linux-next today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-12 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 22:54 [PATCH 0/1] checkpatch: revert broken NOTIFIER_HEAD check john.hubbard
2019-08-11 22:54 ` [PATCH 1/1] " john.hubbard
2019-08-12 1:30 ` Stephen Rothwell [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=20190812113036.7a5dd650@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=gilad@benyossef.com \
--cc=jhubbard@nvidia.com \
--cc=joe@perches.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ofir.drang@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox