From: Ruben Wauters <rubenru09@aol.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
Cc: Ruben Wauters <rubenru09@aol.com>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] staging: sm750fb: cleanup ddk750_sii164
Date: Thu, 17 Apr 2025 20:02:48 +0100 [thread overview]
Message-ID: <20250417190302.13811-1-rubenru09@aol.com> (raw)
In-Reply-To: 20250417190302.13811-1-rubenru09.ref@aol.com
This patch series fixes errors shown by checkpatch.pl in
ddk750_sii164.c and .h
The changes are mostly camelCase to snake_case changes,
however include a variable rename to a clearer name
and removal of the USE_HW_I2C check.
This patch series is created from spliting an earlier
patch into smaller, more logical changes.
The patches will need to be applied in order.
I have included details of the latter within the patch
description itself.
It is also worth noting that I do not have the hardware in
question, so I am unable to test whether any functional
changes would be better served one way or another.
Thank you
Ruben
Ruben Wauters (8):
staging: sm250fb: remove USE_HW_I2C check
staging: sm750fb: rename gDviCtrlChipName
staging: sm750fb: rename vendorID to vendor_id
staging: sm750fb: rename sii164_init_chip params
staging: sm750fb: rename sii164_set_power's param
staging: sm750fb: rename sii164SelectHotPlugDetectionMode
staging: sm750fb: rename detectReg to detect_reg
staging: sm750fb: rename hotPlugValue to hot_plug_value
drivers/staging/sm750fb/ddk750_sii164.c | 119 +++++++++++-------------
drivers/staging/sm750fb/ddk750_sii164.h | 22 ++---
2 files changed, 63 insertions(+), 78 deletions(-)
--
2.45.2
next parent reply other threads:[~2025-04-17 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250417190302.13811-1-rubenru09.ref@aol.com>
2025-04-17 19:02 ` Ruben Wauters [this message]
2025-04-17 19:02 ` [PATCH 1/8] staging: sm250fb: remove USE_HW_I2C check Ruben Wauters
2025-04-18 10:33 ` Greg Kroah-Hartman
2025-04-18 11:42 ` Ruben Wauters
2025-04-17 19:02 ` [PATCH 2/8] staging: sm750fb: rename gDviCtrlChipName Ruben Wauters
2025-04-18 10:36 ` Greg Kroah-Hartman
2025-04-18 11:45 ` Ruben Wauters
2025-04-18 12:09 ` Greg Kroah-Hartman
2025-04-17 19:02 ` [PATCH 3/8] staging: sm750fb: rename vendorID to vendor_id Ruben Wauters
2025-04-18 10:37 ` Greg Kroah-Hartman
2025-04-17 19:02 ` [PATCH 4/8] staging: sm750fb: rename sii164_init_chip params Ruben Wauters
2025-04-17 19:02 ` [PATCH 5/8] staging: sm750fb: rename sii164_set_power's param Ruben Wauters
2025-04-18 10:34 ` Greg Kroah-Hartman
2025-04-17 19:02 ` [PATCH 6/8] staging: sm750fb: rename sii164SelectHotPlugDetectionMode Ruben Wauters
2025-04-17 19:02 ` [PATCH 7/8] staging: sm750fb: rename detectReg to detect_reg Ruben Wauters
2025-04-17 19:02 ` [PATCH 8/8] staging: sm750fb: rename hotPlugValue to hot_plug_value Ruben Wauters
2025-04-18 10:38 ` Greg Kroah-Hartman
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=20250417190302.13811-1-rubenru09@aol.com \
--to=rubenru09@aol.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudip.mukherjee@codethink.co.uk \
--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