[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200513120218.GA982037@kroah.com>
Date: Wed, 13 May 2020 14:02:18 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Anmol <anmol.karan123@...il.com>
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: android: ashmem: Fixed a issue related to
file_operations
On Wed, May 13, 2020 at 05:11:16PM +0530, Anmol wrote:
> From: Anmol <anmol.karan123@...il.com>
>
> Fixed a issue related to struct file_operations which should normally be const.
>
> Signed-off-by: Anmol <anmol.karan123@...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 8044510d8ec6..fbb6ac9ba1ab 100644
> --- a/drivers/staging/android/ashmem.c
> +++ b/drivers/staging/android/ashmem.c
> @@ -367,7 +367,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;
Did you properly build this change?
Also, always use your full name for kernel changes, as the Documentation
states to.
thanks,
greg k-h
Powered by blists - more mailing lists