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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 26 Oct 2017 08:55:06 +1100
From:   NeilBrown <neilb@...e.com>
To:     James Simmons <jsimmons@...radead.org>
Cc:     Oleg Drokin <oleg.drokin@...el.com>,
        Andreas Dilger <andreas.dilger@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        lustre-devel@...ts.lustre.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/9] Assorted cleanups for staging/.../lustre/ldlm/ldlm_flock.c

On Tue, Oct 24 2017, James Simmons wrote:

>> This file contains quite a bit of dead code and unused variables.
>> This patch series cleans it up in various ways.
>> It should change behaviour at all, just code
>> readability/maintainabilty.
>> 
>> I sent the back in July but got not response, possibly because there
>> were included with other patches which caused a distraction.
>> So here they are by themselves.
>
> Thanks for separating them out. I will give them a spin.
>

Thanks.  I have a growing series of cleanups (43 at present, including
these and the namei/dcache patches).  Is posting them here the best
approach?  I assume I should keep them in well-defined groups.  Should I
wait for one set to be merged before sending more, or should I just send
them when I think they are ready and you (or others) will look at them
as time permits.

Thanks,
NeilBrown

Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)

Powered by blists - more mailing lists