linux-kernel - Re: [PATCH 05/19] crypto: proc

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: <2d460de71002200226w5fa27d85maa3fa75e1dca8fdd@mail.gmail.com>
Date:	Sat, 20 Feb 2010 11:26:46 +0100
From:	Richard Hartmann <richih.mailinglist@...il.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-crypto@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Benjamin Gilbert <bgilbert@...cmu.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/19] crypto: proc - Fix checkpatch errors

On Sat, Feb 20, 2010 at 03:48, Herbert Xu <herbert@...dor.apana.org.au> wrote:

>> In this case, please hold seed, tcrypt, wp512 & xcbc. I will
>> refactor them.
>
> OK.

Another workflow question:
Does LKML as a whole prefer rebased patches, patches on top of the
old one or does not one care as long as it's clear what to apply in what
order?
Or does everyone have a different opionion, in which case: What is
yours?

> Thanks for checking.

No need to thank me. You decide what goes in and I accept that.
I signed up to weworking stuff until it suits the relevant maintainer
before I cloned the repo.

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/