linux-kernel - [PATCH] Staging: lustre: lustre: mdc: lproc_mdc.c: declared file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1442406661-3924-1-git-send-email-sakshivaid95@gmail.com>
Date:	Wed, 16 Sep 2015 18:01:01 +0530
From:	Sakshi Vaid <sakshivaid95@...il.com>
To:	oleg.drokin@...el.com
Cc:	andreas.dilger@...el.com, gregkh@...uxfoundation.org,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Sakshi Vaid <sakshivaid95@...il.com>
Subject: [PATCH] Staging: lustre: lustre: mdc: lproc_mdc.c: declared file_operations struct as const

Declared the file_operations structure as const as done elsewhere in the
kernel, as there are no modifiactions to this field.

Following warning found by checkpatch
WARNING: struct file_operations should normally be const

Signed-off-by: Sakshi Vaid <sakshivaid95@...il.com>
---
 drivers/staging/lustre/lustre/mdc/lproc_mdc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/lustre/lustre/mdc/lproc_mdc.c b/drivers/staging/lustre/lustre/mdc/lproc_mdc.c
index c791941..c62c0ac 100644
--- a/drivers/staging/lustre/lustre/mdc/lproc_mdc.c
+++ b/drivers/staging/lustre/lustre/mdc/lproc_mdc.c
@@ -146,7 +146,7 @@ static ssize_t mdc_kuc_write(struct file *file,
 	return count;
 }
 
-struct file_operations mdc_kuc_fops = {
+const struct file_operations mdc_kuc_fops = {
 	.open		= mdc_kuc_open,
 	.write		= mdc_kuc_write,
 	.release	= single_release,
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/