From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: shaikh kamaluddin <shaikhkamal2012@gmail.com>
Cc: "Pavel Skripkin" <paskripkin@gmail.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Hridya Valsaraju" <hridya@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: android: ashmem: Declared file operation with const keyword Warning found by checkpatch.pl script.
Date: Mon, 14 Mar 2022 12:33:42 +0100 [thread overview]
Message-ID: <Yi8oFtMxfTkPF8/h@kroah.com> (raw)
In-Reply-To: <bf27518d-4990-8b0e-c6ea-26a658ce2e54@gmail.com>
On Mon, Mar 14, 2022 at 04:55:55PM +0530, shaikh kamaluddin wrote:
> On 3/13/2022 3:13 AM, Pavel Skripkin wrote:
> > Hi Shaikh,
> >
> > On 3/12/22 23:41, shaikh kamal wrote:
> > > Signed-off-by: shaikh kamal <shaikhkamal2012@gmail.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 ddbde3f8430e..4c6b420fbf4d 100644
> > > --- a/drivers/staging/android/ashmem.c
> > > +++ b/drivers/staging/android/ashmem.c
> > > @@ -377,7 +377,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;
> >
> > Are you sure this patch compiles? vmfile_fops is overrided few lines below
> >
> > odd checkpatch.pl warning...
> >
> >
> >
> >
> > With regards,
> > Pavel Skripkin
>
> Thank you,yes vmfile_fops is overrided in below code.
> Building the kernel - make -j4,
> drivers/staging/android/ashmem.c: In function ‘ashmem_mmap’:
> drivers/staging/android/ashmem.c:431:16: error: assignment of read-only
> variable ‘vmfile_fops’
> vmfile_fops = *vmfile->f_op;
> ^
> drivers/staging/android/ashmem.c:432:21: error: assignment of member ‘mmap’
> in read-only object
> vmfile_fops.mmap = ashmem_vmfile_mmap;
> ^
> drivers/staging/android/ashmem.c:433:34: error: assignment of member
> ‘get_unmapped_area’ in read-only object
> vmfile_fops.get_unmapped_area =
> ^
> scripts/Makefile.build:288: recipe for target
> 'drivers/staging/android/ashmem.o' failed
> make[3]: *** [drivers/staging/android/ashmem.o] Error 1
> scripts/Makefile.build:550: recipe for target 'drivers/staging/android'
> failed
> make[2]: *** [drivers/staging/android] Error 2
> scripts/Makefile.build:550: recipe for target 'drivers/staging' failed
> make[1]: *** [drivers/staging] Error 2
> Makefile:1831: recipe for target 'drivers' failed
As always, it is expected that when you submit a change to the kernel,
at the very least you have test-built it to ensure that it does not
break the build. Please remember to do this next time.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-14 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 20:41 [PATCH] staging: android: ashmem: Declared file operation with const keyword Warning found by checkpatch.pl script shaikh kamal
2022-03-12 21:27 ` Joe Perches
2022-03-14 11:18 ` shaikh kamaluddin
2022-03-12 21:43 ` Pavel Skripkin
2022-03-14 11:25 ` shaikh kamaluddin
2022-03-14 11:33 ` Greg Kroah-Hartman [this message]
2022-03-14 11:55 ` shaikh kamaluddin
2022-03-13 8:01 ` Greg Kroah-Hartman
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=Yi8oFtMxfTkPF8/h@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=maco@android.com \
--cc=paskripkin@gmail.com \
--cc=shaikhkamal2012@gmail.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/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