From: Dorcas AnonoLitunya <anonolitunya@gmail.com>
Cc: anonolitunya@gmail.com, outreachy@lists.linux.dev,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] staging: sm750fb: Renaming camelcase to snakecase
Date: Sun, 15 Oct 2023 23:12:33 +0300 [thread overview]
Message-ID: <cover.1697400022.git.anonolitunya@gmail.com> (raw)
Renames various function names and variable names that were previously
in camelcase to snakecase to ensure consistent naming styles.This issues
were highlighted by checkpatch.
Dorcas AnonoLitunya (5):
Staging: sm750fb: Rename displayControlAdjust_SM750E
Staging: sm750fb: Rename pModeParam
Staging: sm750fb: Rename displayControl
Staging: sm750fb: Rename programModeRegisters
Staging: sm750fb: Rename ddk750_setModeTiming
drivers/staging/sm750fb/ddk750_mode.c | 90 +++++++++++++--------------
drivers/staging/sm750fb/ddk750_mode.h | 2 +-
drivers/staging/sm750fb/sm750_hw.c | 2 +-
3 files changed, 47 insertions(+), 47 deletions(-)
--
2.42.0.345.gaab89be2eb
next reply other threads:[~2023-10-15 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 20:12 Dorcas AnonoLitunya [this message]
2023-10-15 20:12 ` [PATCH 1/5] Staging: sm750fb: Rename displayControlAdjust_SM750E Dorcas AnonoLitunya
2023-10-15 20:22 ` Julia Lawall
2023-10-16 20:29 ` Dorcas Litunya
2023-10-15 20:12 ` [PATCH 2/5] Staging: sm750fb: Rename pModeParam Dorcas AnonoLitunya
2023-10-15 20:12 ` [PATCH 3/5] Staging: sm750fb: Rename displayControl Dorcas AnonoLitunya
2023-10-15 20:23 ` Julia Lawall
2023-10-16 20:30 ` Dorcas Litunya
2023-10-15 20:12 ` [PATCH 4/5] Staging: sm750fb: Rename programModeRegisters Dorcas AnonoLitunya
2023-10-15 20:12 ` [PATCH 5/5] Staging: sm750fb: Rename ddk750_setModeTiming Dorcas AnonoLitunya
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.1697400022.git.anonolitunya@gmail.com \
--to=anonolitunya@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 read-only IMAP folder(s) and NNTP newsgroup(s).