From: Alison Schofield <alison.schofield@intel.com>
To: Aliya Rahmani <aliyarahmani786@gmail.com>
Cc: sudipm.mukherjee@gmail.com, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: sm750fb: Remove volatile
Date: Wed, 13 Apr 2022 18:11:56 -0700 [thread overview]
Message-ID: <20220414011156.GA1243803@alison-desk> (raw)
In-Reply-To: <20220413203914.59533-1-aliyarahmani786@gmail.com>
On Thu, Apr 14, 2022 at 02:09:15AM +0530, Aliya Rahmani wrote:
Hi Aliya,
Wondering why the recipient list different than this:
$ perl scripts/get_maintainer.pl --nogit-fallback --no-rolestats -f drivers/staging/sm750fb/sm750.h
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Teddy Wang <teddy.wang@siliconmotion.com>
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
linux-fbdev@vger.kernel.org
linux-staging@lists.linux.dev
linux-kernel@vger.kernel.org
> 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;
>
> /* function pointers */
> void (*de_init)(struct lynx_accel *accel);
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-04-14 1:10 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 [this message]
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
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=20220414011156.GA1243803@alison-desk \
--to=alison.schofield@intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox