From: Joe Perches <joe@perches.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Use of uninitialized value $line in pattern match
Date: Tue, 06 Mar 2018 07:07:50 -0800 [thread overview]
Message-ID: <1520348870.25605.54.camel@perches.com> (raw)
In-Reply-To: <6B80B875-84A3-4404-BFCB-344D78AA4216@oracle.com>
On Tue, 2018-03-06 at 10:02 -0500, Chuck Lever wrote:
> > On Mar 5, 2018, at 10:00 PM, Joe Perches <joe@perches.com> wrote:
> >
> > On Mon, 2018-03-05 at 16:06 -0500, Chuck Lever wrote:
> > > I think I'm seeing a parsing error in v4.16-rc4 scripts/checkpatch.pl:
> >
> > What I see is your patch is corrupt as the first
> > char of the first context line of the actual patch
> > goto encode_op;
> > does not have a leading space but has a tab.
>
> The patch is generated by:
>
> $ stg export
>
> I confirmed that the e-mailed copy is missing the blank,
> but that my local copy of the patch has a blank there.
> When I do this:
>
> $ scripts/checkpatch.pl patches-nfsd-rdma-for-4.17/nfsd-compound-trace-points
>
> I still get the error output. checkpatch.pl does not misbehave
> with the 27 other patches in that directory.
>
> Is there any debugging output that would be helpful to you?
> This is v4.16-rc4.
Please send me your patch as an attachment.
prev parent reply other threads:[~2018-03-06 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180305210022.18859.37483.stgit@klimt.1015granger.net>
2018-03-05 21:06 ` Use of uninitialized value $line in pattern match Chuck Lever
2018-03-06 3:00 ` Joe Perches
2018-03-06 15:02 ` Chuck Lever
2018-03-06 15:07 ` Joe Perches [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=1520348870.25605.54.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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).