From: Eric Van Hensbergen <ericvh@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: PATCH 2.6.13-rc7-mm1] v9fs: adjust follow_link and put_link to match new VFS API
Date: Sun, 28 Aug 2005 16:35:05 -0500 [thread overview]
Message-ID: <1125264905.17501.26.camel@localhost.localdomain> (raw)
[PATCH] v9fs: adjust follow_link and put_link to match new VFS API
In 2.6.13-rc7 the prototypes for follow_link and put_link were changed
to include support for a cookie to help reclaim resources. This patch
adjusts their definitions in the v9fs implementation.
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
---
commit 30bdd61e96418043a07d2da71bcd757a0341113f
tree 3e268ece4b911b960b47b47182972d8f439667da
parent e189afc5ed8102a56f74cb5be91a6bf3e478a06a
author Eric Van Hensbergen <ericvh@gmail.com> Sun, 28 Aug 2005 16:33:42
-0500
committer Eric Van Hensbergen <ericvh@gmail.com> Sun, 28 Aug 2005
16:33:42 -0500
fs/9p/vfs_inode.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
--- a/fs/9p/vfs_inode.c
+++ b/fs/9p/vfs_inode.c
@@ -1089,7 +1089,7 @@ static int v9fs_vfs_readlink(struct dent
*
*/
-static int v9fs_vfs_follow_link(struct dentry *dentry, struct nameidata
*nd)
+static void *v9fs_vfs_follow_link(struct dentry *dentry, struct
nameidata *nd)
{
int len = 0;
char *link = __getname();
@@ -1109,7 +1109,7 @@ static int v9fs_vfs_follow_link(struct d
}
nd_set_link(nd, link);
- return 0;
+ return NULL;
}
/**
@@ -1119,7 +1119,7 @@ static int v9fs_vfs_follow_link(struct d
*
*/
-static void v9fs_vfs_put_link(struct dentry *dentry, struct nameidata
*nd)
+static void v9fs_vfs_put_link(struct dentry *dentry, struct nameidata
*nd, void *p)
{
char *s = nd_get_link(nd);
reply other threads:[~2005-08-28 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1125264905.17501.26.camel@localhost.localdomain \
--to=ericvh@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).