Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnav Kapoor <kapoorarnav43@gmail.com>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: sm750fb: fix remaining CamelCase issues
Date: Tue, 7 Jul 2026 08:25:46 +0200	[thread overview]
Message-ID: <1ba3f12f-f05d-4301-81b8-2cb1703d0e72@kernel.org> (raw)
In-Reply-To: <20260624042543.38925-1-kapoorarnav43@gmail.com>

On 24/06/2026 06:25, Arnav Kapoor wrote:
> Rename the remaining CamelCase variables and constants
> to follow kernel coding style.
> 
> Rename:
> 
> * powerMode -> power_mode
> * setAllEngOff -> set_all_eng_off
> * resetMemory -> reset_memory
> * sm750_doubleTFT -> SM750_DOUBLE_TFT
> * sm750_dualTFT -> SM750_DUAL_TFT
> 
> Fix build errors by renaming the corresponding
> declarations and enum values as well.
> 
> Reported-by: kernel test robot [lkp@intel.com](mailto:lkp@intel.com)
> Closes: https://lore.kernel.org/oe-kbuild-all/202606240916.wIIrdOzC-lkp@intel.com/
> Signed-off-by: Arnav Kapoor <kapoorarnav43@gmail.com>

Same comments.

Best regards,
Krzysztof

      reply	other threads:[~2026-07-07  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21  4:53 [staging] staging: sm750fb: fix remaining CamelCase issues Arnav Kapoor
2026-06-24  1:51 ` kernel test robot
2026-06-24  3:26 ` kernel test robot
2026-06-24  4:25 ` [PATCH v2] " Arnav Kapoor
2026-07-07  6:25   ` Krzysztof Kozlowski [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=1ba3f12f-f05d-4301-81b8-2cb1703d0e72@kernel.org \
    --to=krzk@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kapoorarnav43@gmail.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