public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amrit Khera <amritkhera98@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Amrit Khera <amritkhera98@gmail.com>,
	arve@android.com, tkjos@android.com, maco@android.com,
	joel@joelfernandes.org, christian@brauner.io, hridya@google.com,
	surenb@google.com, dan.carpenter@oracle.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: android: Fix const keyword style issue in ashmem.c
Date: Fri, 19 Feb 2021 19:10:03 +0530	[thread overview]
Message-ID: <20210219134000.GA25666@amrit> (raw)
In-Reply-To: <YC+rQZoFaT+mPxVL@kroah.com>

On Fri, Feb 19, 2021 at 01:12:49PM +0100, Greg KH wrote:
> On Fri, Feb 19, 2021 at 05:12:38PM +0530, Amrit Khera wrote:
> > This change fixes a checkpatch warning for "struct file_operations
> > should normally be const".
> > 
> > Signed-off-by: Amrit Khera <amritkhera98@gmail.com>
> > ---
> > Changes in v2:
> >  - Wrapped the commit description
> >  - Build tested
> 
> If you tested it, what changed in the diff itself?  Looks the same to
> me...
> 

After further investigating I found that the particular kernel module
was not set in the config file. This did not build it when I built the
kernel. This was making me think that the module was building correctly.

After updating the config, the build indeed breaks. The reason is that
the const keyword cannot be applied here without changing the structure
and flow of the code as the particular variable is later being set in a
condition. Hence, I will be dropping this path for now.

Apologies for the inconvenience caused and thank you for the prompt
replies.

Best Regards,
Amrit Khera

      reply	other threads:[~2021-02-19 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 11:42 [PATCH v2] staging: android: Fix const keyword style issue in ashmem.c Amrit Khera
2021-02-19 12:04 ` Dan Carpenter
2021-02-19 12:12 ` Greg KH
2021-02-19 13:40   ` Amrit Khera [this message]

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=20210219134000.GA25666@amrit \
    --to=amritkhera98@gmail.com \
    --cc=arve@android.com \
    --cc=christian@brauner.io \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hridya@google.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.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