From: eamanu@riseup.net
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] staging: sm750fb: fix CamelCase variables name in sm750
Date: Tue, 26 May 2026 20:30:56 +0000 [thread overview]
Message-ID: <b69100263ea16141b31a7dc240ccdc91@riseup.net> (raw)
In-Reply-To: <2026052623-cause-region-02e3@gregkh>
Hi,
thanks for your reply
On 2026-05-26 13:20, Greg KH wrote:
> On Tue, May 26, 2026 at 10:16:31AM -0300, Emmanuel Arias wrote:
>> Replace CamelCase variable name with snake_case:
>> - pvReg -> pv_reg
>
> Why are you keeping the "pv_"? What does that mean?
Sorry, I'm trying to start contributing in the kernel. I run
scripts/checkpatch.pl --file drivers/staging/sm750fb/*.c
And the output was:
drivers/staging/sm750fb/sm750.c
-------------------------------
WARNING: static const char * array should probably be static const char
* const
#36: FILE: drivers/staging/sm750fb/sm750.c:36:
+static const char *g_fbmode[] = {NULL, NULL};
CHECK: Avoid CamelCase: <pvReg>
#758: FILE: drivers/staging/sm750fb/sm750.c:758:
+ crtc->cursor.mmio = sm750_dev->pvReg +
CHECK: Avoid CamelCase: <setAllEngOff>
#863: FILE: drivers/staging/sm750fb/sm750.c:863:
+ sm750_dev->init_parm.setAllEngOff = 0;
total: 0 errors, 1 warnings, 2 checks, 1171 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or
--fix-inplace.
So I tried to change pvReg for pv_reg and the same for setAllEngOff.
>
>> - setAllEngOff -> set_all_eng_off
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>
> The test robot told you to make this change?
As I understand the test robot failed because:
drivers/staging/sm750fb/sm750_hw.c: In function 'hw_sm750_map':
>> drivers/staging/sm750fb/sm750_hw.c:43:13: error: 'struct sm750_dev' has no member named 'pvReg'; did you mean 'pv_reg'?
sm750_dev->pvReg =
^~~~~
pv_reg
>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202605171049.KbaBnrJV-lkp@intel.com/
>> Signed-off-by: Emmanuel Arias <eamanu@riseup.net>
>> ---
>> drivers/staging/sm750fb/sm750.c | 6 +++---
>> drivers/staging/sm750fb/sm750.h | 4 ++--
>> drivers/staging/sm750fb/sm750_hw.c | 12 ++++++------
>> 3 files changed, 11 insertions(+), 11 deletions(-)
>
> What changed from v1?
So, in this v2 I added sm750_hw.c.
Please let me know if I misunderstood the workflow
>
> thanks,
>
> greg k-h
Cheers,
Emmanuel
prev parent reply other threads:[~2026-05-26 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 13:16 [PATCH v2] staging: sm750fb: fix CamelCase variables name in sm750 Emmanuel Arias
2026-05-26 16:20 ` Greg KH
2026-05-26 20:30 ` eamanu [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=b69100263ea16141b31a7dc240ccdc91@riseup.net \
--to=eamanu@riseup.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--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