From: "M.samet Duman" <dumanmehmetsamet@icloud.com>
To: Ahmet Sezgin Duran <ahmet@sezginduran.net>
Cc: Rupesh Majhi <zoone.rupert@gmail.com>,
gregkh@linuxfoundation.org, sudipm.mukherjee@gmail.com,
teddy.wang@siliconmotion.com, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750: rename CamelCase variable in sm750.c
Date: Fri, 15 May 2026 15:59:18 +0300 [thread overview]
Message-ID: <5A8D2A45-3C03-4D41-96BB-4F2ECC499813@icloud.com> (raw)
In-Reply-To: <03e9e75a-c63c-4a63-88b8-2287daf6c4ad@sezginduran.net>
Not a change that will set the world on fire.
--
Samet
> 2026. 5. 15. 오후 2:46, Ahmet Sezgin Duran <ahmet@sezginduran.net> 작성:
>
> On 5/15/26 1:38 PM, Rupesh Majhi wrote:
>> Renamed the following CamelCase variables to snake_case to comply
>> with Linux kernel coding style:
>> - pvReg -> pv_reg
>> - setAllEngOff -> set_all_eng_off
>> Issue found by checkpatch.
>> Signed-off-by: Rupesh Majhi <zoone.rupert@gmail.com>
>> ---
>> drivers/staging/sm750fb/sm750.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
>> index 996a586a3727..9b30627a19d0 100644
>> --- a/drivers/staging/sm750fb/sm750.c
>> +++ b/drivers/staging/sm750fb/sm750.c
>> @@ -755,7 +755,7 @@ static int lynxfb_set_fbinfo(struct fb_info *info, int index)
>> * must be set after crtc member initialized
>> */
>> crtc->cursor.offset = crtc->o_screen + crtc->vidmem_size - 1024;
>> - crtc->cursor.mmio = sm750_dev->pvReg +
>> + crtc->cursor.mmio = sm750_dev->pv_reg +
>> 0x800f0 + (int)crtc->channel * 0x140;
>> crtc->cursor.max_h = 64;
>> @@ -860,7 +860,7 @@ static void sm750fb_setup(struct sm750_dev *sm750_dev, char *src)
>> sm750_dev->init_parm.mem_clk = 0;
>> sm750_dev->init_parm.master_clk = 0;
>> sm750_dev->init_parm.power_mode = 0;
>> - sm750_dev->init_parm.setAllEngOff = 0;
>> + sm750_dev->init_parm.set_all_eng_off = 0;
>> sm750_dev->init_parm.reset_memory = 1;
>> /* defaultly turn g_hwcursor on for both view */
>> @@ -1059,7 +1059,7 @@ static void lynxfb_pci_remove(struct pci_dev *pdev)
>> sm750fb_framebuffer_release(sm750_dev);
>> arch_phys_wc_del(sm750_dev->mtrr.vram);
>> - iounmap(sm750_dev->pvReg);
>> + iounmap(sm750_dev->pv_reg);
>> iounmap(sm750_dev->vmem);
>> pci_release_region(pdev, 1);
>> kfree(g_settings);
>
> Did you compile this patch?
>
> Regards,
> Ahmet Sezgin Duran
>
next prev parent reply other threads:[~2026-05-15 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 10:38 [PATCH] staging: sm750: rename CamelCase variable in sm750.c Rupesh Majhi
2026-05-15 11:18 ` Ahmet Sezgin Duran
2026-05-15 12:59 ` M.samet Duman [this message]
2026-05-15 13:13 ` Greg KH
[not found] ` <CABpb+S7EcSUnmnCn_aRURnVON39Jyrxe3oktnPphyOFzpaTU0g@mail.gmail.com>
2026-05-15 17:19 ` Ahmet Sezgin Duran
2026-05-15 22:35 ` kernel test robot
2026-05-15 23:48 ` kernel test robot
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=5A8D2A45-3C03-4D41-96BB-4F2ECC499813@icloud.com \
--to=dumanmehmetsamet@icloud.com \
--cc=ahmet@sezginduran.net \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=zoone.rupert@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