linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kisub Choe <kisub.choe.0x1@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
	linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: rename 'proc_setBLANK'
Date: Wed, 18 Jun 2025 16:26:10 +0200	[thread overview]
Message-ID: <2025061817-jacket-nacho-50d6@gregkh> (raw)
In-Reply-To: <20250618141555.5434-1-kisub.choe.0x1@gmail.com>

On Wed, Jun 18, 2025 at 11:15:55PM +0900, Kisub Choe wrote:
> Rename 'proc_setBLANK' to 'proc_setBLANK' to

That doesn't rename anything :(



> conform with kernel style guidelines as reported by checkpatch.pl
> 
> CHECK: Avoid CamelCase: <proc_setBLANK>
> 
> Signed-off-by: Kisub Choe <kisub.choe.0x1@gmail.com>
> ---
>  drivers/staging/sm750fb/sm750.c | 4 ++--
>  drivers/staging/sm750fb/sm750.h | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index 1d929aca399c..bb2ade6030c2 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -577,7 +577,7 @@ static int lynxfb_ops_blank(int blank, struct fb_info *info)
>  	pr_debug("blank = %d.\n", blank);
>  	par = info->par;
>  	output = &par->output;
> -	return output->proc_setBLANK(output, blank);
> +	return output->proc_set_blank(output, blank);
>  }
>  
>  static int sm750fb_set_drv(struct lynxfb_par *par)
> @@ -605,7 +605,7 @@ static int sm750fb_set_drv(struct lynxfb_par *par)
>  	crtc->ypanstep = 1;
>  	crtc->ywrapstep = 0;
>  
> -	output->proc_setBLANK = (sm750_dev->revid == SM750LE_REVISION_ID) ?
> +	output->proc_set_blank = (sm750_dev->revid == SM750LE_REVISION_ID) ?
>  				 hw_sm750le_set_blank : hw_sm750_set_blank;

Why do we even need this function pointer?  Why not just do the check
above when it is called instead of this indirection?

thanks,

greg k-h

  reply	other threads:[~2025-06-18 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 14:15 [PATCH] staging: sm750fb: rename 'proc_setBLANK' Kisub Choe
2025-06-18 14:26 ` Greg KH [this message]
2025-06-19 13:12   ` [PATCH v2] " Kisub Choe
2025-06-19 13:24     ` Greg KH
2025-06-19 13:49       ` Kisub Choe
2025-06-19 13:52         ` Greg KH
2025-06-19 14:22           ` Kisub Choe

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=2025061817-jacket-nacho-50d6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=kisub.choe.0x1@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@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;
as well as URLs for NNTP newsgroup(s).