From: Joe Perches <joe@perches.com>
To: Allen Hubbe <allenbh@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch: fix perl warning about unescaped brace
Date: Fri, 29 Jul 2016 18:51:43 -0700 [thread overview]
Message-ID: <1469843503.3998.100.camel@perches.com> (raw)
In-Reply-To: <CAJ80sauof_OuADqRw_pEawbGWMOLaLQveuoTo-jerKZE_BmP6A@mail.gmail.com>
On Fri, 2016-07-29 at 21:41 -0400, Allen Hubbe wrote:
> Mystery solved... and drop this patch.
>
> My 'master' on this system was set to an old ref, v4.2-rc1. There are
> no perl warnings as of v4.7.
OK great, thanks.
I had just built and tested with 5.24 and didn't see
any warnings and wondered a bit.
next prev parent reply other threads:[~2016-07-30 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 22:27 [PATCH] checkpatch: if no filenames then read stdin Allen Hubbe
2016-07-29 22:27 ` [PATCH] checkpatch: fix perl warning about unescaped brace Allen Hubbe
2016-07-29 23:06 ` Joe Perches
2016-07-29 23:57 ` Allen Hubbe
2016-07-30 1:41 ` Allen Hubbe
2016-07-30 1:51 ` Joe Perches [this message]
2016-07-29 23:35 ` [PATCH] checkpatch: if no filenames then read stdin Joe Perches
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=1469843503.3998.100.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=allenbh@gmail.com \
--cc=apw@canonical.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 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.