From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs proc.c
Date: 18 Jul 2006 21:18:48 -0000 [thread overview]
Message-ID: <20060718211848.28605.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2006-07-18 21:18:48
Modified files:
gfs-kernel/src/gfs: proc.c
Log message:
Rename req_lock to gfs_req_lock to avoid duplicate symbols.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/proc.c.diff?cvsroot=cluster&r1=1.9&r2=1.10
--- cluster/gfs-kernel/src/gfs/proc.c 2006/07/18 20:48:20 1.9
+++ cluster/gfs-kernel/src/gfs/proc.c 2006/07/18 21:18:48 1.10
@@ -32,7 +32,7 @@
struct semaphore gfs_fs_lock;
char *gfs_proc_margs;
spinlock_t gfs_proc_margs_lock;
-spinlock_t req_lock;
+spinlock_t gfs_req_lock;
/**
* gfs_proc_fs_add - Add a FS to the list of mounted FSs
@@ -357,10 +357,10 @@
{
char *p;
- spin_lock(&req_lock);
+ spin_lock(&gfs_req_lock);
p = file->private_data;
file->private_data = NULL;
- spin_unlock(&req_lock);
+ spin_unlock(&gfs_req_lock);
if (p)
kfree(p);
@@ -378,9 +378,9 @@
return -EFAULT;
}
- spin_lock(&req_lock);
+ spin_lock(&gfs_req_lock);
file->private_data = p;
- spin_unlock(&req_lock);
+ spin_unlock(&gfs_req_lock);
return size;
}
@@ -401,10 +401,10 @@
char *p;
int error;
- spin_lock(&req_lock);
+ spin_lock(&gfs_req_lock);
p = file->private_data;
file->private_data = NULL;
- spin_unlock(&req_lock);
+ spin_unlock(&gfs_req_lock);
if (!p)
return -ENOENT;
@@ -472,7 +472,7 @@
init_MUTEX(&gfs_fs_lock);
gfs_proc_margs = NULL;
spin_lock_init(&gfs_proc_margs_lock);
- spin_lock_init(&req_lock);
+ spin_lock_init(&gfs_req_lock);
pde = create_proc_entry("fs/gfs", S_IFREG | 0600, NULL);
if (!pde)
reply other threads:[~2006-07-18 21:18 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=20060718211848.28605.qmail@sourceware.org \
--to=rpeterso@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.