From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Florin <ericflorin@google.com>
Cc: teddy.wang@siliconmotion.com, sudipm.mukherjee@gmail.com,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: sm750fb: rename dpPortBase in lynx_accel
Date: Wed, 21 May 2025 13:47:40 +0200 [thread overview]
Message-ID: <2025052125-stew-customs-4ca9@gregkh> (raw)
In-Reply-To: <97fcc39f3e63f465c49e8725d10f7c43fd35cd85.1747605658.git.ericflorin@google.com>
On Sun, May 18, 2025 at 03:09:47PM -0700, Eric Florin wrote:
> Rename `dpPortBase` to `dp_port_base` to conform with kernel style
> guidelines as reported by checkpatch.pl
>
> CHECK: Avoid CamelCase: <dpPortBase>
>
> Signed-off-by: Eric Florin <ericflorin@google.com>
> ---
> drivers/staging/sm750fb/sm750.h | 2 +-
> drivers/staging/sm750fb/sm750_accel.c | 2 +-
> drivers/staging/sm750fb/sm750_hw.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/sm750.h b/drivers/staging/sm750fb/sm750.h
> index a2342c69a65a..0ed1e18611ba 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 *dpr_base;
> /* base virtual address of de data port */
> - volatile unsigned char __iomem *dpPortBase;
> + volatile unsigned char __iomem *dp_port_base;
Same here, are you sure this doesn't come directly from the hardware
spec?
thanks,
greg k-h
prev parent reply other threads:[~2025-05-21 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 22:09 [PATCH 0/2] staging: sm750fb: style cleanup in `lynx_accel` Eric Florin
2025-05-18 22:09 ` [PATCH 1/2] staging: sm750fb: rename dprBase to dpr_base Eric Florin
2025-05-21 11:47 ` Greg KH
2025-05-18 22:09 ` [PATCH 2/2] staging: sm750fb: rename dpPortBase in lynx_accel Eric Florin
2025-05-21 11:47 ` Greg KH [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=2025052125-stew-customs-4ca9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ericflorin@google.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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;
as well as URLs for NNTP newsgroup(s).