From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@linux-foundation.org, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 7/9] const: make file_lock_operations const
Date: Thu, 10 Sep 2009 03:20:54 +0400 [thread overview]
Message-ID: <20090909232054.GG2881@x200.localdomain> (raw)
In-Reply-To: <20090909231518.GA2881@x200.localdomain>
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
fs/afs/flock.c | 2 +-
fs/lockd/clntproc.c | 2 +-
fs/nfs/nfs4state.c | 2 +-
include/linux/fs.h | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--- a/fs/afs/flock.c
+++ b/fs/afs/flock.c
@@ -21,7 +21,7 @@ static void afs_fl_release_private(struct file_lock *fl);
static struct workqueue_struct *afs_lock_manager;
static DEFINE_MUTEX(afs_lock_manager_mutex);
-static struct file_lock_operations afs_lock_ops = {
+static const struct file_lock_operations afs_lock_ops = {
.fl_copy_lock = afs_fl_copy_lock,
.fl_release_private = afs_fl_release_private,
};
--- a/fs/lockd/clntproc.c
+++ b/fs/lockd/clntproc.c
@@ -458,7 +458,7 @@ static void nlmclnt_locks_release_private(struct file_lock *fl)
nlm_put_lockowner(fl->fl_u.nfs_fl.owner);
}
-static struct file_lock_operations nlmclnt_lock_ops = {
+static const struct file_lock_operations nlmclnt_lock_ops = {
.fl_copy_lock = nlmclnt_locks_copy_lock,
.fl_release_private = nlmclnt_locks_release_private,
};
--- a/fs/nfs/nfs4state.c
+++ b/fs/nfs/nfs4state.c
@@ -638,7 +638,7 @@ static void nfs4_fl_release_lock(struct file_lock *fl)
nfs4_put_lock_state(fl->fl_u.nfs4_fl.owner);
}
-static struct file_lock_operations nfs4_fl_lock_ops = {
+static const struct file_lock_operations nfs4_fl_lock_ops = {
.fl_copy_lock = nfs4_fl_copy_lock,
.fl_release_private = nfs4_fl_release_lock,
};
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1067,7 +1067,7 @@ struct file_lock {
struct fasync_struct * fl_fasync; /* for lease break notifications */
unsigned long fl_break_time; /* for nonblocking lease breaks */
- struct file_lock_operations *fl_ops; /* Callbacks for filesystems */
+ const struct file_lock_operations *fl_ops; /* Callbacks for filesystems */
struct lock_manager_operations *fl_lmops; /* Callbacks for lockmanagers */
union {
struct nfs_lock_info nfs_fl;
next prev parent reply other threads:[~2009-09-09 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:15 [PATCH 1/9] const: make struct super_block::dq_op const Alexey Dobriyan
2009-09-09 23:16 ` [PATCH 2/9] const: make struct super_block::s_qcop const Alexey Dobriyan
2009-09-09 23:17 ` [PATCH 3/9] const: mark remaining super_operations const Alexey Dobriyan
2009-09-09 23:18 ` [PATCH 4/9] const: mark remaining export_operations const Alexey Dobriyan
2009-09-09 23:19 ` [PATCH 5/9] const: mark remaining address_space_operations const Alexey Dobriyan
2009-09-09 23:20 ` [PATCH 6/9] const: mark remaining inode_operations as const Alexey Dobriyan
2009-09-09 23:20 ` Alexey Dobriyan [this message]
2009-09-09 23:21 ` [PATCH 8/9] const: make lock_manager_operations const Alexey Dobriyan
2009-09-09 23:22 ` [PATCH 9/9] const: make block_device_operations const Alexey Dobriyan
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=20090909232054.GG2881@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).