From: Charalampos Mitrodimas <charmitro@posteo.net>
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,
outreachy@lists.linux.dev,
Charalampos Mitrodimas <charmitro@posteo.net>
Subject: [PATCH 3/8] staging: sm750fb: Rename sii164GetChipString to sii164_get_chip_string
Date: Mon, 13 Nov 2023 15:05:08 +0000 [thread overview]
Message-ID: <20231113150512.1210869-4-charmitro@posteo.net> (raw)
In-Reply-To: <20231113150512.1210869-1-charmitro@posteo.net>
Signed-off-by: Charalampos Mitrodimas <charmitro@posteo.net>
---
drivers/staging/sm750fb/ddk750_dvi.c | 2 +-
drivers/staging/sm750fb/ddk750_sii164.c | 4 ++--
drivers/staging/sm750fb/ddk750_sii164.h | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_dvi.c b/drivers/staging/sm750fb/ddk750_dvi.c
index 6dee95e60a6e..e568c210e2bd 100644
--- a/drivers/staging/sm750fb/ddk750_dvi.c
+++ b/drivers/staging/sm750fb/ddk750_dvi.c
@@ -19,7 +19,7 @@ static struct dvi_ctrl_device dcft_supported_dvi_controller[] = {
.get_device_id = sii164_get_device_id,
#ifdef SII164_FULL_FUNCTIONS
.reset_chip = sii164_reset_chip,
- .get_chip_string = sii164GetChipString,
+ .get_chip_string = sii164_get_chip_string,
.set_power = sii164SetPower,
.enable_hot_plug_detection = sii164EnableHotPlugDetection,
.is_connected = sii164IsConnected,
diff --git a/drivers/staging/sm750fb/ddk750_sii164.c b/drivers/staging/sm750fb/ddk750_sii164.c
index 284c32f7e9b4..f0a255da1b36 100644
--- a/drivers/staging/sm750fb/ddk750_sii164.c
+++ b/drivers/staging/sm750fb/ddk750_sii164.c
@@ -261,13 +261,13 @@ void sii164_reset_chip(void)
}
/*
- * sii164GetChipString
+ * sii164_get_chip_string
* This function returns a char string name of the current DVI Controller
* chip.
*
* It's convenient for application need to display the chip name.
*/
-char *sii164GetChipString(void)
+char *sii164_get_chip_string(void)
{
return gDviCtrlChipName;
}
diff --git a/drivers/staging/sm750fb/ddk750_sii164.h b/drivers/staging/sm750fb/ddk750_sii164.h
index 7a71f94a1e9b..7c5cc81f38d4 100644
--- a/drivers/staging/sm750fb/ddk750_sii164.h
+++ b/drivers/staging/sm750fb/ddk750_sii164.h
@@ -32,7 +32,7 @@ unsigned short sii164_get_device_id(void);
#ifdef SII164_FULL_FUNCTIONS
void sii164_reset_chip(void);
-char *sii164GetChipString(void);
+char *sii164_get_chip_string(void);
void sii164SetPower(unsigned char powerUp);
void sii164EnableHotPlugDetection(unsigned char enableHotPlug);
unsigned char sii164IsConnected(void);
--
2.39.2
next prev parent reply other threads:[~2023-11-13 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 15:05 [PATCH 0/8] staging: sm750fb: Multiple camel cases renames Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 1/8] staging: sm750fb: Rename sii164GetDeviceID to sii164_get_device_id Charalampos Mitrodimas
2023-11-23 12:49 ` Greg KH
2023-11-13 15:05 ` [PATCH 2/8] staging: sm750fb: Rename sii164ResetChip to sii164_reset_chip Charalampos Mitrodimas
2023-11-13 15:05 ` Charalampos Mitrodimas [this message]
2023-11-13 15:05 ` [PATCH 4/8] staging: sm750fb: Rename sii164SetPower to sii164_set_power Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 5/8] staging: sm750fb: Rename sii164EnableHotPlugDetection to sii164_enable_hot_plug_detection Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 6/8] staging: sm750fb: Rename sii164IsConnected to sii164_is_connected Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 7/8] staging: sm750fb: Rename sii164CheckInterrupt to sii164_check_interrupt Charalampos Mitrodimas
2023-11-13 15:05 ` [PATCH 8/8] staging: sm750fb: Rename sii164ClearInterrupt to sii164_clear_interrupt Charalampos Mitrodimas
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=20231113150512.1210869-4-charmitro@posteo.net \
--to=charmitro@posteo.net \
--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