From: sandeen@sandeen.net
To: xfs@oss.sgi.com
Subject: [PATCH] collapse sv_init, init_sv on linux
Date: Thu, 24 Aug 2006 21:23:52 -0500 (CDT) [thread overview]
Message-ID: <20060825022352.7E22C18DAFEC7@sandeen.net> (raw)
Change the one caller of init_sv on linux2.4 to sv_init, since there
is no difference between sv_init & init_sv on linux anyway.
Then get rid of now unused init_sv.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
linux-2.4/sv.h | 2 --
linux-2.4/xfs_vnode.c | 2 +-
linux-2.6/sv.h | 2 --
3 files changed, 1 insertion(+), 5 deletions(-)
Index: xfs-linux/linux-2.4/sv.h
===================================================================
--- xfs-linux.orig/linux-2.4/sv.h
+++ xfs-linux/linux-2.4/sv.h
@@ -53,8 +53,6 @@ static inline void _sv_wait(sv_t *sv, sp
remove_wait_queue(&sv->waiters, &wait);
}
-#define init_sv(sv,type,name,flag) \
- init_waitqueue_head(&(sv)->waiters)
#define sv_init(sv,flag,name) \
init_waitqueue_head(&(sv)->waiters)
#define sv_destroy(sv) \
Index: xfs-linux/linux-2.4/xfs_vnode.c
===================================================================
--- xfs-linux.orig/linux-2.4/xfs_vnode.c
+++ xfs-linux/linux-2.4/xfs_vnode.c
@@ -35,7 +35,7 @@ vn_init(void)
register int i;
for (svp = vsync, i = 0; i < NVSYNC; i++, svp++)
- init_sv(svp, SV_DEFAULT, "vsy", i);
+ sv_init(svp, SV_DEFAULT, "vsy");
}
struct bhv_vnode *
Index: xfs-linux/linux-2.6/sv.h
===================================================================
--- xfs-linux.orig/linux-2.6/sv.h
+++ xfs-linux/linux-2.6/sv.h
@@ -53,8 +53,6 @@ static inline void _sv_wait(sv_t *sv, sp
remove_wait_queue(&sv->waiters, &wait);
}
-#define init_sv(sv,type,name,flag) \
- init_waitqueue_head(&(sv)->waiters)
#define sv_init(sv,flag,name) \
init_waitqueue_head(&(sv)->waiters)
#define sv_destroy(sv) \
next reply other threads:[~2006-08-25 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 2:23 sandeen [this message]
2006-08-25 2:34 ` [PATCH] collapse sv_init, init_sv on linux Nathan Scott
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=20060825022352.7E22C18DAFEC7@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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