All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aliya <aliyarahmani786@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sudipm.mukherjee@gmail.com, linux-staging@lists.linux.dev,
	 outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: sm750fb: Remove volatile
Date: Thu, 14 Apr 2022 19:30:44 +0530	[thread overview]
Message-ID: <CAGTWmRFs7dc2wusqdhND4vc=tT38iw6OHzrzN_3pskLtegnyNA@mail.gmail.com> (raw)
In-Reply-To: <YlfFhZ0o/FSzxOvE@kroah.com>

On Thu, Apr 14, 2022 at 12:26 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Apr 14, 2022 at 02:09:15AM +0530, Aliya Rahmani wrote:
> > Remove volatile to fix checkpatch.pl warning.
> >
> > Signed-off-by: Aliya Rahmani <aliyarahmani786@gmail.com>
> > ---
> >  drivers/staging/sm750fb/sm750.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/sm750fb/sm750.h b/drivers/staging/sm750fb/sm750.h
> > index aff69661c8e6..7a11f8593596 100644
> > --- a/drivers/staging/sm750fb/sm750.h
> > +++ b/drivers/staging/sm750fb/sm750.h
> > @@ -52,7 +52,7 @@ struct lynx_accel {
> >       /* base virtual address of DPR registers */
> >       volatile unsigned char __iomem *dprBase;
> >       /* base virtual address of de data port */
> > -     volatile unsigned char __iomem *dpPortBase;
> > +     unsigned char __iomem *dpPortBase;
>
> So you have properly determined that this code is now fixed and does not
> require this volatile marking?  :)
>
> Please don't blindly follow checkpatch suggestions without understanding
> what they do.  While the use of volatile is probably wrong here, you
> need to ensure that you can successfully remove this so you need to
> prove it in the changelog text that all is still ok.
>
> Also, why did you only remove one?
>
> thanks,
>
> greg k-h

My apologies, I'll verify and understand the code before following
checkpatch suggestions.

Thanks,
Aliya

  reply	other threads:[~2022-04-14 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 20:39 [PATCH] staging: sm750fb: Remove volatile Aliya Rahmani
2022-04-14  1:11 ` Alison Schofield
2022-04-14  6:06   ` Aliya
2022-04-14 15:16     ` Alison Schofield
2022-04-14  6:56 ` Greg KH
2022-04-14 14:00   ` Aliya [this message]
2022-04-14 10:33 ` Dan Carpenter

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='CAGTWmRFs7dc2wusqdhND4vc=tT38iw6OHzrzN_3pskLtegnyNA@mail.gmail.com' \
    --to=aliyarahmani786@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=sudipm.mukherjee@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.