From: Nick Piggin <npiggin@suse.de>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
mhalcrow@us.ibm.com
Subject: Re: [PATCH] Convert ecryptfs to use new aops
Date: Thu, 25 Sep 2008 01:22:14 +0200 [thread overview]
Message-ID: <20080924232214.GA30307@wotan.suse.de> (raw)
In-Reply-To: <1222293448.6491.49.camel@badari-desktop>
On Wed, Sep 24, 2008 at 02:57:28PM -0700, Badari Pulavarty wrote:
> Hi Andrew,
>
> As part of moving all the filesystems to make use of new aops to
> eventually remove prepare/commit_write, here is the patch to convert
> ecryptfs to make use of new aops.
>
> Originally written by Nick, I did few minor fixes and clean ups.
> Michael Halcrow tested and confirmed that it works.
>
> Thanks,
> Badari
Hey, thanks very much for taking the initiative on these, I appreciate
it, and you're getting the most important thing done which is getting
testing and review :)
next prev parent reply other threads:[~2008-09-24 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 21:57 [PATCH] Convert ecryptfs to use new aops Badari Pulavarty
2008-09-24 23:22 ` Nick Piggin [this message]
2008-09-26 21:53 ` Dave Kleikamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080924232214.GA30307@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=pbadari@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.