[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X+l8m6Z7eD26gaUC@kroah.com>
Date: Mon, 28 Dec 2020 07:35:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: jovin555 <jovin555@...il.com>
Cc: devel@...verdev.osuosl.org, Todd Kjos <tkjos@...roid.com>,
linux-kernel@...r.kernel.org,
Arve Hjønnevåg <arve@...roid.com>,
Joel Fernandes <joel@...lfernandes.org>,
Martijn Coenen <maco@...roid.com>,
Christian Brauner <christian@...uner.io>
Subject: Re: [PATCH] staging: android: ashmem: Declared file operation with
const keyword
On Mon, Dec 28, 2020 at 12:13:00AM -0500, jovin555 wrote:
> Warning found by checkpatch.pl script.
>
> Signed-off-by: jovin555 <jovin555@...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 c05a214191da..f9cfa15b785f 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;
> struct ashmem_area *asma = file->private_data;
> int ret = 0;
>
Did you build your modified kernel with this change in it?
Always do so...
greg k-h
Powered by blists - more mailing lists