Re: [PATCH 0/8] staging: sm750fb: change function naming style

On Sat, Apr 05, 2025 at 02:00:51PM +0100, Richard Akintola wrote:
> Address checkpatch's "Avoid camelCase" for sm750fb module by changing
> function name to conform to kernel code style.
> 
> The patches are required to be applied in sequence.
> 
> Richard Akintola (8):
>   staging: sm750fb: change sii164GetDeviceID to snake_case
>   staging: sm750fb: change sii164ResetChip to snake_case
>   staging: sm750fb: change sii164SetPower to snake_case
>   staging: sm750fb: change sii164GetChipString to snake_case
>   staging: sm750fb: change sii164EnableHotPlugDetection to snake_case
>   staging: sm750fb: change sii164IsConnected to snake_case
>   staging: sm750fb: change sii164CheckInterrupt to snake_case
>   staging: sm750fb: change sii164ClearInterrupt to snake_case
> 
>  drivers/staging/sm750fb/ddk750_dvi.c    | 16 +++++-----
>  drivers/staging/sm750fb/ddk750_sii164.c | 42 ++++++++++++-------------
>  drivers/staging/sm750fb/ddk750_sii164.h | 16 +++++-----
>  3 files changed, 37 insertions(+), 37 deletions(-)
> 
> -- 
> 2.39.5
> 
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot