linux-kernel - Re: [PATCH 0/3] Refactor event related code

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 for Android: free password hash cracker in your pocket

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

Message-ID: <316061dd4135befde8e6fa34d7705108@posteo.de>
Date:   Mon, 25 Sep 2017 12:25:01 +0200
From:   Martin Kepplinger <martink@...teo.de>
To:     harinath Nampally <harinath922@...il.com>
Cc:     Jonathan Cameron <jic23@...nel.org>, knaack.h@....de,
        lars@...afoo.de, Peter Meerwald-Stadler <pmeerw@...erw.net>,
        Greg KH <gregkh@...uxfoundation.org>,
        linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
        Alison Schofield <amsfield22@...il.com>
Subject: Re: [PATCH 0/3] Refactor event related code

Am 25.09.2017 12:16 schrieb harinath Nampally:
>> First, this is at least v2 of this series. Second, it still seems to 
>> include
>> a 4th unrelated patch.
> ok I was not sure whether to make it v2 as the change was to only cover 
> letter
> and no code changes. But now I know, will send v3 of this series.
> 

as soon as you don't do an exact resend, increment the version number. 
When
reviewers can ignore all previous versions, they instantly know. And for 
the case
we still want to look at everything, you should include a persistent 
revision history
description below the email's --- dashes.

But actually you should have read this and much more in the 
Documentation
directory before sending.