From: Greg KH <gregkh@linuxfoundation.org>
To: Jamal Shareef <jamal.k.shareef@gmail.com>
Cc: boqun.feng@microsoft.com, andrea.parri@microsoft.com,
sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/4] staging: sm750fb: Edit CamelCase in ddk750_dvi.c
Date: Wed, 16 Oct 2019 14:35:54 -0700 [thread overview]
Message-ID: <20191016213554.GA906859@kroah.com> (raw)
In-Reply-To: <0ccb65c7e5844541bb96a791c39caabb05a49afb.1571260724.git.jamal.k.shareef@gmail.com>
On Wed, Oct 16, 2019 at 02:20:45PM -0700, Jamal Shareef wrote:
> Edit CamelCase naming convention in ddk750_dvi.c file.
> Issue found by checkpatch.
>
> Edit depends on related files which are also being patched
> as part of the patchset.
>
> Signed-off-by: Jamal Shareef <jamal.k.shareef@gmail.com>
> ---
> drivers/staging/sm750fb/ddk750_dvi.c | 68 ++++++++++++++--------------
> 1 file changed, 34 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/ddk750_dvi.c b/drivers/staging/sm750fb/ddk750_dvi.c
> index cd564ea40779..6fa77d4effef 100644
> --- a/drivers/staging/sm750fb/ddk750_dvi.c
> +++ b/drivers/staging/sm750fb/ddk750_dvi.c
> @@ -11,50 +11,50 @@
> * function API. Please set the function pointer to NULL whenever the function
> * is not supported.
> */
> -static struct dvi_ctrl_device g_dcftSupportedDviController[] = {
> +static struct dvi_ctrl_device g_dcft_supported_dvi_controller[] = {
> #ifdef DVI_CTRL_SII164
> {
> - .pfnInit = sii164InitChip,
> - .pfnGetVendorId = sii164GetVendorID,
> - .pfnGetDeviceId = sii164GetDeviceID,
> + .pfn_init = sii164_init_chip,
> + .pfn_get_vendor_id = sii164_get_vendor_id,
> + .pfn_get_device_id = sii164_get_device_id,
> #ifdef SII164_FULL_FUNCTIONS
> - .pfnResetChip = sii164ResetChip,
> - .pfnGetChipString = sii164GetChipString,
> - .pfnSetPower = sii164SetPower,
> - .pfnEnableHotPlugDetection = sii164EnableHotPlugDetection,
> - .pfnIsConnected = sii164IsConnected,
> - .pfnCheckInterrupt = sii164CheckInterrupt,
> - .pfnClearInterrupt = sii164ClearInterrupt,
> + .pfn_reset_chip = sii164_reset_chip,
> + .pfn_get_chip_string = sii164_get_chip_string,
> + .pfn_set_power = sii164_set_power,
> + .pfn_enable_hot_plug_detection = sii164_enable_hot_plug_detection,
> + .pfn_is_connected = sii164_is_connected,
> + .pfn_check_interrupt = sii164_check_interrupt,
> + .pfn_clear_interrupt = sii164_clear_interrupt,
> #endif
> },
> #endif
> };
>
> -int dviInit(unsigned char edge_select,
> - unsigned char bus_select,
> - unsigned char dual_edge_clk_select,
> - unsigned char hsync_enable,
> - unsigned char vsync_enable,
> - unsigned char deskew_enable,
> - unsigned char deskew_setting,
> - unsigned char continuous_sync_enable,
> - unsigned char pll_filter_enable,
> - unsigned char pll_filter_value)
> +int dvi_init(unsigned char edge_select,
You didn't also change the .h file at the same time, how did this build?
You can't break the build at any point in time, every patch must work
properly.
Ah, no one even calls this function, maybe that's why this works? If
so, just delete the function entirely!
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-16 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 21:20 [PATCH 0/4] Edit CamelCase in sm750fb dvi and sii164 files Jamal Shareef
2019-10-16 21:20 ` [PATCH 1/4] staging: sm750fb: Edit CamelCase in ddk750_dvi.c Jamal Shareef
2019-10-16 21:30 ` [Outreachy kernel] " Julia Lawall
2019-10-16 21:35 ` Greg KH [this message]
2019-10-17 1:38 ` Jamal Shareef
2019-10-17 12:53 ` Greg KH
2019-10-17 21:52 ` Jamal Shareef
2019-10-17 22:10 ` Greg KH
2019-10-16 21:20 ` [PATCH 2/4] staging: sm750fb: Edit CamelCase in ddk750_dvi.h Jamal Shareef
2019-10-16 21:20 ` [PATCH 3/4] staging: sm750fb: Edit CamelCase in ddk750_sii164.c Jamal Shareef
2019-10-16 21:20 ` [PATCH 4/4] staging: sm750fb: Edit CamelCase in ddk750_sii164.h Jamal Shareef
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=20191016213554.GA906859@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrea.parri@microsoft.com \
--cc=boqun.feng@microsoft.com \
--cc=jamal.k.shareef@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--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 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.