Date: Fri, 2 Nov 2007 13:10:31 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, ecryptfs-devel@lists.sourceforge.net,
       trevor.highland@gmail.com
Subject: Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto
 operation
Message-Id: <20071102131031.3369e6e6.akpm@linux-foundation.org>
In-Reply-To: <20071102185308.GC30760@localhost.austin.ibm.com>
References: <20071102185033.GB30487@localhost.austin.ibm.com>
	<20071102185308.GC30760@localhost.austin.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 881
Lines: 21

On Fri, 2 Nov 2007 13:53:08 -0500
Michael Halcrow <mhalcrow@us.ibm.com> wrote:

> There is no need to keep re-setting the same key for any given
> eCryptfs inode. This patch optimizes the use of the crypto API and
> helps performance a bit.
> 
> Signed-off-by: Trevor Highland <trevor.highland@gmail.com>
> Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>

I've inferred from this that Michael authored this patch.  Please
let me know if that was incorrect.

The way in which we indicate authorship is to put a From: line right
at the top of the changelog.  If no such line appears then the From:
line from the mail headers is used.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/