linux-kernel - Re: [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1427916771.31790.73.camel@perches.com>
Date:	Wed, 01 Apr 2015 12:32:51 -0700
From:	Joe Perches <joe@...ches.com>
To:	Janakarajan Natarajan <janakarajann@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes

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>]"



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/