From: Joe Perches <joe@perches.com>
To: Janakarajan Natarajan <janakarajann@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes
Date: Wed, 01 Apr 2015 12:32:51 -0700 [thread overview]
Message-ID: <1427916771.31790.73.camel@perches.com> (raw)
In-Reply-To: <CAJo0J4w7EPyc7mmugkEoh5Tvar_e_zT1V9bb1oWU9kAhgQYTkQ@mail.gmail.com>
On Wed, 2015-04-01 at 12:23 -0700, Janakarajan Natarajan wrote:
> I initially sent a single patch on March 11th. It was recommended that I
> send it in a patchset as it did too many things in 1 patch.
> I submitted the v2 patchset on March 12th. After a week of not knowing if
> it was accepted, I resent it again on March 18.
>
> I will resend the patchset. Should it be labled 'v2'?
People can be busy and for most patches that aren't
critical fixes, you should wait a month or so before
resending anything that hasn't been applied or
commented on.
And instead of incrementing the version, just prefix
with something like: "[resend PATCH v<N>]"
next prev parent reply other threads:[~2015-04-01 19:32 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 ` [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes Greg Kroah-Hartman
[not found] ` <CAJo0J4xzWVjEhTe1-N24PJOzSPbZQbksyWzHCk5X+nYxmWmS6Q@mail.gmail.com>
2015-03-31 16:00 ` Greg Kroah-Hartman
[not found] ` <CAJo0J4w7EPyc7mmugkEoh5Tvar_e_zT1V9bb1oWU9kAhgQYTkQ@mail.gmail.com>
2015-04-01 19:32 ` Joe Perches [this message]
-- 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=1427916771.31790.73.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=janakarajann@gmail.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).