From: Jeff Layton <jlayton@redhat.com>
To: linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 05/10] cifs: rename cifs_iget to cifs_root_iget
Date: Wed, 27 May 2009 16:34:02 -0400 [thread overview]
Message-ID: <1243456447-11176-6-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1243456447-11176-1-git-send-email-jlayton@redhat.com>
The current cifs_iget isn't suitable for anything but the root inode.
Rename it with a more appropriate name.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
---
fs/cifs/cifsfs.c | 2 +-
fs/cifs/cifsfs.h | 2 +-
fs/cifs/inode.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c
index 5e6d358..0a10a59 100644
--- a/fs/cifs/cifsfs.c
+++ b/fs/cifs/cifsfs.c
@@ -146,7 +146,7 @@ cifs_read_super(struct super_block *sb, void *data,
#endif
sb->s_blocksize = CIFS_MAX_MSGSIZE;
sb->s_blocksize_bits = 14; /* default 2**14 = CIFS_MAX_MSGSIZE */
- inode = cifs_iget(sb, ROOT_I);
+ inode = cifs_root_iget(sb, ROOT_I);
if (IS_ERR(inode)) {
rc = PTR_ERR(inode);
diff --git a/fs/cifs/cifsfs.h b/fs/cifs/cifsfs.h
index 051b71c..3b6a85c 100644
--- a/fs/cifs/cifsfs.h
+++ b/fs/cifs/cifsfs.h
@@ -36,7 +36,7 @@ extern void cifs_read_inode(struct inode *);
/* Functions related to inodes */
extern const struct inode_operations cifs_dir_inode_ops;
-extern struct inode *cifs_iget(struct super_block *, unsigned long);
+extern struct inode *cifs_root_iget(struct super_block *, unsigned long);
extern int cifs_create(struct inode *, struct dentry *, int,
struct nameidata *);
extern struct dentry *cifs_lookup(struct inode *, struct dentry *,
diff --git a/fs/cifs/inode.c b/fs/cifs/inode.c
index 7fb9694..fad882b 100644
--- a/fs/cifs/inode.c
+++ b/fs/cifs/inode.c
@@ -696,7 +696,7 @@ char *cifs_build_path_to_root(struct cifs_sb_info *cifs_sb)
}
/* gets root inode */
-struct inode *cifs_iget(struct super_block *sb, unsigned long ino)
+struct inode *cifs_root_iget(struct super_block *sb, unsigned long ino)
{
int xid;
struct cifs_sb_info *cifs_sb;
--
1.6.2.2
next prev parent reply other threads:[~2009-05-27 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 20:33 [PATCH 00/10] cifs: implement proper hardlink handling (try #5) Jeff Layton
2009-05-27 20:33 ` [PATCH 01/10] cifs: have cifs_NTtimeToUnix take a little-endian arg Jeff Layton
2009-05-27 20:33 ` [PATCH 02/10] cifs: make cnvrtDosUnixTm take a little-endian args and an offset Jeff Layton
2009-05-27 20:34 ` [PATCH 03/10] cifs: reorganize get_cifs_acl Jeff Layton
2009-05-28 15:23 ` Shirish Pargaonkar
2009-05-27 20:34 ` [PATCH 04/10] cifs: clean up set_cifs_acl interfaces Jeff Layton
2009-05-28 15:23 ` [linux-cifs-client] " Shirish Pargaonkar
2009-05-27 20:34 ` Jeff Layton [this message]
2009-05-27 20:34 ` [PATCH 06/10] cifs: add new cifs_iget function and convert unix codepath to use it Jeff Layton
2009-05-27 20:34 ` [PATCH 07/10] cifs: convert cifs_get_inode_info and non-posix readdir to use cifs_iget Jeff Layton
2009-05-27 20:34 ` [PATCH 08/10] cifs: make serverino the default when mounting Jeff Layton
2009-05-27 20:34 ` [PATCH 09/10] cifs: remove cifsInodeInfo->inUse counter Jeff Layton
2009-05-27 20:34 ` [PATCH 10/10] cifs: remove "hardlink detection" from cifs_rename Jeff Layton
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=1243456447-11176-6-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).