All of lore.kernel.org
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs lm_interface.h
Date: 4 Aug 2006 19:55:30 -0000	[thread overview]
Message-ID: <20060804195530.25858.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2006-08-04 19:55:30

Modified files:
	gfs-kernel/src/gfs: lm_interface.h 

Log message:
	bring lm_interface.h in sync with the version in gfs2

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/lm_interface.h.diff?cvsroot=cluster&r1=1.1&r2=1.2

--- cluster/gfs-kernel/src/gfs/lm_interface.h	2006/01/09 21:12:24	1.1
+++ cluster/gfs-kernel/src/gfs/lm_interface.h	2006/08/04 19:55:30	1.2
@@ -1,6 +1,6 @@
 /*
  * Copyright (C) Sistina Software, Inc.  1997-2003 All rights reserved.
- * Copyright (C) 2004-2005 Red Hat, Inc.  All rights reserved.
+ * Copyright (C) 2004-2006 Red Hat, Inc.  All rights reserved.
  *
  * This copyrighted material is made available to anyone wishing to use,
  * modify, copy, or redistribute it subject to the terms and conditions
@@ -260,11 +260,16 @@
 	int ls_flags;
 };
 
-void __init gfs_init_lmh(void);
+void __init gfs2_init_lmh(void);
 
 /*
  * 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);
@@ -276,15 +281,15 @@
  * unmounting a file system.
  */
 
-int gfs_mount_lockproto(char *proto_name, char *table_name, char *host_data,
-			lm_callback_t cb, lm_fsdata_t *fsdata,
-			unsigned int min_lvb_size, int flags,
-			struct lm_lockstruct *lockstruct,
-			struct kobject *fskobj);
+int gfs2_mount_lockproto(char *proto_name, char *table_name, char *host_data,
+			 lm_callback_t cb, lm_fsdata_t *fsdata,
+			 unsigned int min_lvb_size, int flags,
+			 struct lm_lockstruct *lockstruct,
+			 struct kobject *fskobj);
 
-void gfs_unmount_lockproto(struct lm_lockstruct *lockstruct);
+void gfs2_unmount_lockproto(struct lm_lockstruct *lockstruct);
 
-void gfs_withdraw_lockproto(struct lm_lockstruct *lockstruct);
+void gfs2_withdraw_lockproto(struct lm_lockstruct *lockstruct);
 
 #endif /* __LM_INTERFACE_DOT_H__ */
 



             reply	other threads:[~2006-08-04 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 19:55 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-07 14:20 [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=20060804195530.25858.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.