From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
phillip@hellewell.homeip.net
Subject: Re: [PATCH] ecryptfs: superblock cleanups
Date: Fri, 13 Oct 2006 10:09:21 -0500 [thread overview]
Message-ID: <20061013150921.GB3513@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610131040020.17802@sbz-30.cs.Helsinki.FI>
On Fri, Oct 13, 2006 at 10:41:21AM +0300, Pekka J Enberg wrote:
> - Kill useless ecryptfs_set_superblock_private wrapper
> - Rename ecryptfs_superblock_to_private to ecryptfs_sb for readability
Okay, but if we are going to do this for the superblock info struct,
why not do it for all objects (file, dentry, and inode) in order to
maintain naming consistency? That would be a pretty large, yet
functionally trivial, patch. Is there a general interest in doing
this?
prev parent reply other threads:[~2006-10-13 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 7:41 Pekka J Enberg
2006-10-13 15:09 ` Michael Halcrow [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=20061013150921.GB3513@us.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=phillip@hellewell.homeip.net \
/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
all inboxes | Powered by JetHome®