linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Akintola <princerichard17a@gmail.com>
To: outreachy@lists.linux.dev
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
	gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Richard Akintola <princerichard17a@gmail.com>
Subject: [PATCH 0/8] staging: sm750fb: change function naming style
Date: Sat,  5 Apr 2025 14:00:51 +0100	[thread overview]
Message-ID: <cover.1743857160.git.princerichard17a@gmail.com> (raw)

Address checkpatch's "Avoid camelCase" for sm750fb module by changing
function name to conform to kernel code style.

The patches are required to be applied in sequence.

Richard Akintola (8):
  staging: sm750fb: change sii164GetDeviceID to snake_case
  staging: sm750fb: change sii164ResetChip to snake_case
  staging: sm750fb: change sii164SetPower to snake_case
  staging: sm750fb: change sii164GetChipString to snake_case
  staging: sm750fb: change sii164EnableHotPlugDetection to snake_case
  staging: sm750fb: change sii164IsConnected to snake_case
  staging: sm750fb: change sii164CheckInterrupt to snake_case
  staging: sm750fb: change sii164ClearInterrupt to snake_case

 drivers/staging/sm750fb/ddk750_dvi.c    | 16 +++++-----
 drivers/staging/sm750fb/ddk750_sii164.c | 42 ++++++++++++-------------
 drivers/staging/sm750fb/ddk750_sii164.h | 16 +++++-----
 3 files changed, 37 insertions(+), 37 deletions(-)

-- 
2.39.5


             reply	other threads:[~2025-04-05 13:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 13:00 Richard Akintola [this message]
2025-04-05 13:00 ` [PATCH 1/8] staging: sm750fb: change sii164GetDeviceID to snake_case Richard Akintola
2025-04-05 13:00 ` [PATCH 2/8] staging: sm750fb: change sii164ResetChip " Richard Akintola
2025-04-05 13:00 ` [PATCH 3/8] staging: sm750fb: change sii164SetPower " Richard Akintola
2025-04-05 13:00 ` [PATCH 4/8] staging: sm750fb: change sii164GetChipString " Richard Akintola
2025-04-05 13:00 ` [PATCH 5/8] staging: sm750fb: change sii164EnableHotPlugDetection " Richard Akintola
2025-04-05 13:00 ` [PATCH 6/8] staging: sm750fb: change sii164IsConnected " Richard Akintola
2025-04-05 13:00 ` [PATCH 7/8] staging: sm750fb: change sii164CheckInterrupt " Richard Akintola
2025-04-05 13:00 ` [PATCH 8/8] staging: sm750fb: change sii164ClearInterrupt " Richard Akintola
2025-04-05 13:35 ` [PATCH 0/8] staging: sm750fb: change function naming style Greg KH
2025-04-05 14:07   ` Richard Akintola
2025-04-05 14:16     ` Samuel Abraham
2025-04-05 14:23       ` Samuel Abraham
2025-04-07  5:57       ` Richard Akintola
2025-04-07  5:59         ` Greg KH
2025-04-07  6:23           ` Richard Akintola
2025-04-08 10:38           ` Richard Akintola
2025-04-08 10:47             ` Greg KH
2025-04-08 11:03               ` Richard Akintola

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=cover.1743857160.git.princerichard17a@gmail.com \
    --to=princerichard17a@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@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).