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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d460de71002160356l6c26d513qba7d0cece32daddd@mail.gmail.com>
Date:	Tue, 16 Feb 2010 12:56:15 +0100
From:	Richard Hartmann <richih.mailinglist@...il.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	linux-crypto@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] CRYPTO: Fix checkpatch errors & warnings in cipher.c

On Thu, Feb 11, 2010 at 05:46, Herbert Xu <herbert@...dor.apana.org.au> wrote:

>> Should I re-send the patch or is it less noise & hassle if I just leave
>> it this way?
>
> You don't have to resend it.

GregKH said that I should just re-send all patches after a week. OTOH, I
am not sure if this is not a little bit too agressive.

Thus, I wanted to check if I should wait some more or what the general
consensus of action in the crypto subtree is.

And yes, I am aware that janitor work, and thus my patches, is very low
priority.


Thanks,
Richard
--
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