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-next>] [day] [month] [year] [list]
Date:	Sat, 23 May 2015 13:14:28 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Michael Shuey <shuey@...due.edu>
Cc:	"Drokin, Oleg" <oleg.drokin@...el.com>, devel@...verdev.osuosl.org,
	gregkh@...uxfoundation.org, kernel-janitors@...r.kernel.org,
	linux-kernel@...r.kernel.org, HPDD-discuss@...1.01.org,
	lustre-devel@...ts.lustre.org
Subject: Re: [PATCH v4 00/13] staging: lustre: lnet: code cleanups

We would have applied the v3 patchset but now I don't know because we're
up to v5.  We can't apply v5 because there are problems with it.  No
one responded to v3 so Greg still might apply it or he might find these
email threads too scrambled and delete everything and ask for a resend.

It's pretty messed up so just wait for Greg to get to it before sending
more patches?

Basically you should only send patches which you assume will be applied.
If no one responds after 3 days then probably that means everyone from
the peanut gallery (Me, Sudip, Joe, the lustre devs), we don't have an
issue.  Then Greg does the last review (2-3 weeks later perhaps).  But
if it makes it past all the other reviews then generally Greg also will
be ok with it.

Greg applies patches in first come, first applied order.  If they don't
apply then you have to redo it.  He doesn't invest a lot of time into
figuring out why.  So you have to coordinate with the other devs, it's
up to you how you do that.

regards,
dan carpenter

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ