[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YC+Vt0qJbkCLPZfo@kroah.com>
Date: Fri, 19 Feb 2021 11:40:55 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Amrit Khera <amritkhera98@...il.com>
Cc: arve@...roid.com, tkjos@...roid.com, maco@...roid.com,
joel@...lfernandes.org, christian@...uner.io, hridya@...gle.com,
surenb@...gle.com, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: android: Fix const keyword style issue in
ashmem.c
On Fri, Feb 19, 2021 at 03:43:39PM +0530, Amrit Khera wrote:
> This change fixes a checkpatch warning for "struct file_operations should normally be const".
>
> Signed-off-by: Amrit Khera <amritkhera98@...il.com>
> ---
> drivers/staging/android/ashmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
> index d66a64e42273..7854fd410efa 100644
> --- a/drivers/staging/android/ashmem.c
> +++ b/drivers/staging/android/ashmem.c
> @@ -376,7 +376,7 @@ ashmem_vmfile_get_unmapped_area(struct file *file, unsigned long addr,
>
> static int ashmem_mmap(struct file *file, struct vm_area_struct *vma)
> {
> - static struct file_operations vmfile_fops;
> + static const struct file_operations vmfile_fops;
> struct ashmem_area *asma = file->private_data;
> int ret = 0;
>
Always test-build your patches before sending them out, otherwise you
are wasting reviewer's time, right?
:(
Powered by blists - more mailing lists