From: Joe Perches <joe@perches.com>
To: shaikh kamal <shaikhkamal2012@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"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: Sat, 12 Mar 2022 13:27:37 -0800 [thread overview]
Message-ID: <19a139d0dde6fadfce79c10d40c9810b50702fb1.camel@perches.com> (raw)
In-Reply-To: <20220312204128.3942-1-shaikhkamal2012@gmail.com>
On Sun, 2022-03-13 at 03:11 +0530, shaikh kamal wrote:
[]
> diff --git 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;
Make sure to compile any files modified by your suggested patches
_before_ sending the patches.
next prev parent reply other threads:[~2022-03-12 22:06 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 [this message]
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
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=19a139d0dde6fadfce79c10d40c9810b50702fb1.camel@perches.com \
--to=joe@perches.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.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=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