From: Joe Perches <joe@perches.com>
To: Bhakti Priya <bhaktipriya96@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexander Kuleshov <kuleshovmail@gmail.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Andreas Ruprecht <andreas.ruprecht@fau.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723au: Fixes unnecessary return warning
Date: Fri, 29 Jan 2016 23:24:53 -0800 [thread overview]
Message-ID: <1454138693.3524.1.camel@perches.com> (raw)
In-Reply-To: <CAFNHFT9nosMWgAvDdhvpMQLa2+02kD-wk0ChuZWpvCbLGMFYOg@mail.gmail.com>
On Sat, 2016-01-30 at 12:23 +0530, Bhakti Priya wrote:
> I will be happy to extend checkpatch.pl. As suggested by you, I am
> trying to detect such blank lines in a line removal patch by checking
> if the line above the deleted line was a blank line and the line
> following the deleted line had a closing brace.
> Can you please guide me and let me know if I am headed in the right
> direction.
You have to track all the + and - lines that precede the
deleted line.
Good luck.
next prev parent reply other threads:[~2016-01-30 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 17:29 [PATCH] staging: rtl8723au: Fixes unnecessary return warning Bhaktipriya Shridhar
2016-01-29 18:00 ` Jes Sorensen
2016-01-29 23:17 ` Julian Calaby
2016-01-30 1:28 ` Joe Perches
2016-01-30 3:09 ` Julian Calaby
2016-01-30 3:18 ` Joe Perches
2016-01-30 6:53 ` Bhakti Priya
2016-01-30 7:24 ` Joe Perches [this message]
2016-01-30 12:02 ` Julian Calaby
2016-01-30 12:09 ` Joe Perches
2016-01-31 14:31 ` Jes Sorensen
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=1454138693.3524.1.camel@perches.com \
--to=joe@perches.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=andreas.ruprecht@fau.de \
--cc=bhaktipriya96@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=julian.calaby@gmail.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).