[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <b86916f54cd6a22e0aa1d7570c0e1c793a3025e2.1503813780.git.arvind.yadav.cs@gmail.com>
Date: Sun, 27 Aug 2017 11:35:27 +0530
From: Arvind Yadav <arvind.yadav.cs@...il.com>
To: oleg.drokin@...el.com, andreas.dilger@...el.com,
jsimmons@...radead.org, gregkh@...uxfoundation.org,
john.hammond@...el.com
Cc: linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
lustre-devel@...ts.lustre.org
Subject: [PATCH] staging: lustre: constify cl_lock_operations
cl_lock_operations are not supposed to change at runtime.
cl_lock_slice_add is working with const cl_lock_operations.
So mark the non-const cl_lock_operations structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@...il.com>
---
drivers/staging/lustre/lustre/obdecho/echo_client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/obdecho/echo_client.c b/drivers/staging/lustre/lustre/obdecho/echo_client.c
index 1c4a8fe..b3fbc3c 100644
--- a/drivers/staging/lustre/lustre/obdecho/echo_client.c
+++ b/drivers/staging/lustre/lustre/obdecho/echo_client.c
@@ -319,7 +319,7 @@ static void echo_lock_fini(const struct lu_env *env,
kmem_cache_free(echo_lock_kmem, ecl);
}
-static struct cl_lock_operations echo_lock_ops = {
+static const struct cl_lock_operations echo_lock_ops = {
.clo_fini = echo_lock_fini,
};
--
2.7.4
Powered by blists - more mailing lists