From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Janakarajan Natarajan <janakarajann@gmail.com>
Cc: Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes
Date: Thu, 26 Mar 2015 11:07:03 +0100 [thread overview]
Message-ID: <20150326100703.GA8999@kroah.com> (raw)
In-Reply-To: <1426712196-7288-1-git-send-email-janakarajann@gmail.com>
On Wed, Mar 18, 2015 at 01:56:31PM -0700, Janakarajan Natarajan wrote:
> Minor changes to fix ft1000 driver checkpatch.pl warnings
>
> Janakarajan Natarajan (5):
> Drivers: Staging: ft1000: Single line if-statement changes
> Drivers: Staging: ft1000: Fix extra parenthesis warnings
> Drivers: Staging: ft1000: Refactoring if-else statement
> Drivers: Staging: ft1000: Fix blank line after declartion warning
> Drivers: Staging: ft1000: checkpatch.pl header file warning fix
>
> v2: if-else refactored as suggested by Joe Perches <joe@perches.co
> Variable reworked as suggested by Giedrius Statkevicius <giedrius.statkevicius@gmail.com>
>
> drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c | 16 +++++++---------
> drivers/staging/ft1000/ft1000-usb/ft1000_debug.c | 6 ++----
> 2 files changed, 9 insertions(+), 13 deletions(-)
Why did you resend this "v2" series with no changes?
I don't know what to do here, so I've dropped all of your pending
patches for this driver, please resend anything I haven't applied.
Remember, you need to be _really_ explicit as to what to do, I deal with
over a thousand emails a day, and handle patches in batches, and have no
short-term memory as to what happened yesterday/last week in email
threads.
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-26 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 20:56 [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes Janakarajan Natarajan
2015-03-18 20:56 ` [PATCHv2 1/5] Drivers: Staging: ft1000: Single line if-statement changes Janakarajan Natarajan
2015-03-18 20:56 ` [PATCHv2 2/5] Drivers: Staging: ft1000: Fix extra parenthesis warnings Janakarajan Natarajan
2015-03-18 20:56 ` [PATCHv2 3/5] Drivers: Staging: ft1000: Refactoring if-else statement Janakarajan Natarajan
2015-03-18 20:56 ` [PATCHv2 4/5] Drivers: Staging: ft1000: Fix blank line warning Janakarajan Natarajan
2015-03-18 20:56 ` [PATCHv2 5/5] Drivers: Staging: ft1000: checkpatch.pl header file warning fix Janakarajan Natarajan
2015-03-26 10:07 ` Greg Kroah-Hartman [this message]
[not found] ` <CAJo0J4xzWVjEhTe1-N24PJOzSPbZQbksyWzHCk5X+nYxmWmS6Q@mail.gmail.com>
2015-03-31 16:00 ` [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes Greg Kroah-Hartman
[not found] ` <CAJo0J4w7EPyc7mmugkEoh5Tvar_e_zT1V9bb1oWU9kAhgQYTkQ@mail.gmail.com>
2015-04-01 19:32 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 21:03 [PATCH 1/1] Drivers: Staging: ft1000: checkpatch warning fixes Janakarajan Natarajan
2015-03-13 2:42 ` [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes Janakarajan Natarajan
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=20150326100703.GA8999@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=janakarajann@gmail.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;
as well as URLs for NNTP newsgroup(s).