[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f5804e0d-974d-36b2-3247-747187d1f135@infradead.org>
Date: Thu, 15 Oct 2020 22:16:45 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: kiransuren@...osl.org, kirank.suren@...il.com,
gregkh@...uxfoundation.org
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: android: ashmem: changed struct file_operations
to const file_operations
On 10/15/20 10:11 PM, kiransuren@...osl.org wrote:
> From: kiransuren <kirank.suren@...il.com>
>
> Fixed a coding style issue.
>
> Signed-off-by: Kiran Surendran <kirank.suren@...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 10b4be1f3e78..f2b67c4fe8d2 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 file_operations vmfile_fops;
> struct ashmem_area *asma = file->private_data;
> int ret = 0;
>
>
Did you build/compile this change? My brain syntax checker doesn't like it.
and what coding style issue?
--
~Randy
Powered by blists - more mailing lists