From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs lm_interface.h
Date: 7 Aug 2006 14:20:29 -0000 [thread overview]
Message-ID: <20060807142029.18920.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-08-07 14:20:29
Modified files:
gfs-kernel/src/gfs: lm_interface.h
Log message:
update lm_interface.h from version in git tree
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/lm_interface.h.diff?cvsroot=cluster&r1=1.2&r2=1.3
--- cluster/gfs-kernel/src/gfs/lm_interface.h 2006/08/04 19:55:30 1.2
+++ cluster/gfs-kernel/src/gfs/lm_interface.h 2006/08/07 14:20:29 1.3
@@ -265,16 +265,11 @@
/*
* Lock module bottom interface. A lock module makes itself available to GFS
* with these functions.
- *
- * For the time being, we copy the gfs1 lock module bottom interface so the
- * same lock modules can be used with both gfs1 and gfs2 (it won't be possible
- * to load both gfs1 and gfs2 at once.) Eventually the lock modules will fork
- * for gfs1/gfs2 and this API can change to the gfs2_ prefix.
*/
-int gfs_register_lockproto(struct lm_lockops *proto);
+int gfs2_register_lockproto(struct lm_lockops *proto);
-void gfs_unregister_lockproto(struct lm_lockops *proto);
+void gfs2_unregister_lockproto(struct lm_lockops *proto);
/*
* Lock module top interface. GFS calls these functions when mounting or
next reply other threads:[~2006-08-07 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:20 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 19:55 [Cluster-devel] cluster/gfs-kernel/src/gfs lm_interface.h teigland
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=20060807142029.18920.qmail@sourceware.org \
--to=teigland@sourceware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.