From: Dorine Tipo <dorine.a.tipo@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev
Cc: Dorine Tipo <dorine.a.tipo@gmail.com>
Subject: [PATCH v3 0/8] Rename variables in sm750fb driver
Date: Wed, 6 Mar 2024 05:44:50 +0000 [thread overview]
Message-ID: <20240306054458.102288-1-dorine.a.tipo@gmail.com> (raw)
Hello,
This V2 series addresses the Avoid CamelCase checkpatch warning by renaming
the variables in sm750fb driver to use snake_case.
Patch 1 renames variable sii164GetDeviceID to sii164_get_device_id.
Patch 2 renames variable sii164ResetChip to sii164_reset_chip.
Patch 3 renames variable sii164GetChipString to sii164_get_chip_string.
Patch 4 renames variable sii164SetPower to sii164_set_power.
Patch 5 renames variable sii164EnableHotPlugDetection to
sii164_enable_hot_plug_detection.
Patch 6 renames variable sii164IsConnected to sii164_is_connected.
Patch 7 renames variable sii164CheckInterrupt to sii164_check_interrupt.
Patch 8 renames variable sii164ClearInterrupt to sii164_clear_interrupt.
Updates since V1:
Incorporated feedback from <gregkh@linuxfoundation.org> to fix the
warnings in the patches and create a patch series for the same.
I have also compiled the entire kernel and it compiled successfully.
(I understand this is not sufficient and would be happy to run further
tests. Should I run kselftests on the module?)
Updates since V2:
Incorporated feedback from <dan.carpenter@linaro.org> and reverted the
sii164GetDeviceID since it breaks the build.
Dorine Tipo (8):
Staging: sm750fb: Rename sii164ResetChip
Staging: sm750fb: Rename variable sii164GetChipString
Staging: sm750fb: Rename variable sii164SetPower
Staging: sm750fb: Rename variable sii164EnableHotPlugDetection
Staging: sm750fb: Rename variable sii164IsConnected
Staging: sm750fb: Rename variable sii164CheckInterrupt
Staging: sm750fb: Rename Variable sii164ClearInterrupt
Revert "Staging: sm750fb: Rename variable sii164GetDeviceID"
drivers/staging/sm750fb/ddk750_dvi.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2024-03-07 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 5:44 Dorine Tipo [this message]
2024-03-06 5:44 ` [PATCH v3 1/8] Staging: sm750fb: Rename sii164ResetChip Dorine Tipo
2024-03-07 14:06 ` Dan Carpenter
2024-03-07 14:21 ` Greg KH
2024-03-08 9:10 ` Apology and Request for Resubmitting Patch Dorine Tipo
2024-03-08 9:52 ` Julia Lawall
2024-03-09 12:48 ` Dan Carpenter
2024-03-06 5:44 ` [PATCH v3 2/8] Staging: sm750fb: Rename variable sii164GetChipString Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 3/8] Staging: sm750fb: Rename variable sii164SetPower Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 4/8] Staging: sm750fb: Rename variable sii164EnableHotPlugDetection Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 5/8] Staging: sm750fb: Rename variable sii164IsConnected Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 6/8] Staging: sm750fb: Rename variable sii164CheckInterrupt Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 7/8] Staging: sm750fb: Rename Variable sii164ClearInterrupt Dorine Tipo
2024-03-06 5:44 ` [PATCH v3 8/8] Revert "Staging: sm750fb: Rename variable sii164GetDeviceID" Dorine Tipo
2024-03-07 14:20 ` Greg KH
2024-03-07 17:12 ` [PATCH v3 0/8] Rename variables in sm750fb driver Julia Lawall
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=20240306054458.102288-1-dorine.a.tipo@gmail.com \
--to=dorine.a.tipo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.