On Fri, Nov 02, 2007 at 01:10:31PM -0700, Andrew Morton wrote: > On Fri, 2 Nov 2007 13:53:08 -0500 > Michael Halcrow <[email protected]> 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 <[email protected]> > > Signed-off-by: Michael Halcrow <[email protected]> > > I've inferred from this that Michael authored this patch. Please > let me know if that was incorrect. Trevor Highland actually authored this one. > 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. Noted. Mike
Attachment:
pgpRyHIx9EeFV.pgp
Description: PGP signature
- References:
- [PATCH 0/3] eCryptfs: extent offset fix, crypto performance, and larger header regions
- From: Michael Halcrow <[email protected]>
- [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
- From: Michael Halcrow <[email protected]>
- Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
- From: Andrew Morton <[email protected]>
- [PATCH 0/3] eCryptfs: extent offset fix, crypto performance, and larger header regions
- Prev by Date: Re: [2.6 patch] kernel/power/: move function prototypes to header
- Next by Date: Re: [PATCH] add_partition silently ignored errors
- Previous by thread: Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
- Next by thread: Error in __bread reading a 4K block from a SATA device
- Index(es):