From: Julia Lawall <julia.lawall@lip6.fr>
To: Shraddha Barke <shraddha.6596@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Frank Zago <fzago@cray.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging : lustre: Struct file_operations should be const
Date: Sun, 2 Aug 2015 13:26:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1508021322120.2048@localhost6.localdomain6> (raw)
In-Reply-To: <1438513366-23462-1-git-send-email-shraddha.6596@gmail.com>
On Sun, 2 Aug 2015, Shraddha Barke wrote:
> This patch fixes the following checkpatch.pl warning:
>
> WARNING: struct file_operations should normally be const
This is not the good way to write the message. The information it conveys
is "checkpatch generated this warning, so I have made some change
(unspecified) that make checkpatch not complain".
A better approach would be to say:
Declare the file_operations structure ll_file_operations as const, as done
elsewhere in the kernel, as there are no modifications to its fields.
Problem found using checkpatch.
This way the reader knows what was done, and what issues were taken into
account when making the change. At the same time, you still credit
checkpatch for helping you find the problem
julia
>
> Signed-off-by: Shraddha Barke <shraddha.6596@gmail.com>
> ---
> drivers/staging/lustre/lustre/llite/file.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/lustre/lustre/llite/file.c b/drivers/staging/lustre/lustre/llite/file.c
> index dcd0c6d..369a722 100644
> --- a/drivers/staging/lustre/lustre/llite/file.c
> +++ b/drivers/staging/lustre/lustre/llite/file.c
> @@ -3116,7 +3116,7 @@ int ll_inode_permission(struct inode *inode, int mask)
> }
>
> /* -o localflock - only provides locally consistent flock locks */
> -struct file_operations ll_file_operations = {
> +const struct file_operations ll_file_operations = {
> .read_iter = ll_file_read_iter,
> .write_iter = ll_file_write_iter,
> .unlocked_ioctl = ll_file_ioctl,
> --
> 2.1.0
>
>
next prev parent reply other threads:[~2015-08-02 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 11:02 Shraddha Barke
2015-08-02 11:26 ` Julia Lawall [this message]
2015-08-02 17:34 ` [PATCH v2] Revert "Staging : lustre: Struct file_operations should be const" Shraddha Barke
2015-08-03 5:29 ` Sudip Mukherjee
2015-08-03 5:47 [PATCH] Staging : lustre: Struct file_operations should be const Shraddha Barke
2015-08-03 7:18 ` Sudip Mukherjee
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=alpine.DEB.2.02.1508021322120.2048@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=fzago@cray.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=shraddha.6596@gmail.com \
--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
all inboxes | Powered by JetHome®