From: Dustin Kirkland <kirkland@canonical.com>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: Tyler Hicks <tyhicks@linux.vnet.ibm.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ecryptfs: fix interpose/interpolate typos in comments
Date: Thu, 14 Jan 2010 12:29:10 -0600 [thread overview]
Message-ID: <1263493750.20132.44.camel@x200> (raw)
In-Reply-To: <201001042317.o04NH2wC001198@agora.fsl.cs.sunysb.edu>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Mon, 2010-01-04 at 18:17 -0500, Erez Zadok wrote:
> Ecryptfs: fix interpose/interpolate typos in comments
>
> Signed-off-by: Erez Zadok <ezk@cs.sunysb.edu>
> diff --git a/fs/ecryptfs/main.c b/fs/ecryptfs/main.c
> index 427588a..58c699e 100644
> --- a/fs/ecryptfs/main.c
> +++ b/fs/ecryptfs/main.c
> @@ -590,8 +590,8 @@ out:
> * with as much information as it can before needing
> * the lower filesystem.
> * ecryptfs_read_super(): this accesses the lower filesystem and uses
> - * ecryptfs_interpolate to perform most of the linking
> - * ecryptfs_interpolate(): links the lower filesystem into ecryptfs
> + * ecryptfs_interpose to perform most of the linking
> + * ecryptfs_interpose(): links the lower filesystem into ecryptfs (inode.c)
> */
> static int ecryptfs_get_sb(struct file_system_type *fs_type, int flags,
> const char *dev_name, void *raw_data,
Looks fine to me. Thanks, Erez. Sorry for the delay.
Acked-by: Dustin Kirkland <kirkland@canonical.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-01-14 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 23:17 [PATCH] ecryptfs: fix interpose/interpolate typos in comments Erez Zadok
2010-01-14 18:29 ` Dustin Kirkland [this message]
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=1263493750.20132.44.camel@x200 \
--to=kirkland@canonical.com \
--cc=ezk@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tyhicks@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).