public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Karolina Stolarek <karolina.stolarek@intel.com>
To: Dorcas AnonoLitunya <anonolitunya@gmail.com>
Cc: <outreachy@lists.linux.dev>, <julia.lawall@inria.fr>,
	<dan.carpenter@linaro.org>, <andi.shyti@linux.intel.com>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	<linux-fbdev@vger.kernel.org>, <linux-staging@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Staging: sm750fb: Rename display_control_adjust_sm750LE
Date: Wed, 18 Oct 2023 10:12:19 +0200	[thread overview]
Message-ID: <870b9b74-75bc-2a0d-7138-ae8df237f980@intel.com> (raw)
In-Reply-To: <20231018080416.25931-2-anonolitunya@gmail.com>

On 18.10.2023 10:04, Dorcas AnonoLitunya wrote:
> Rename function display_control_adjust_sm750LE to
> display_control_adjust_sm750le. This further enforces snakecase naming
> convention for consistent naming style throughout entire file.
> 
> This change was suggested by Andi Shyti <andi.shyti@linux.intel.com>

You can use Suggested-by tag here, if you wish (as per [1]) before 
Signed-off-by line.

In the first line of the commit, "Staging" should be lowercase.

All the best,
Karolina

-----
[1] - Documentation/process/submitting-patches.rst

> 
> Signed-off-by: Dorcas AnonoLitunya <anonolitunya@gmail.com>
> ---
> 
> v2: Correctly spells Andi Shyti's name
> 
>   drivers/staging/sm750fb/ddk750_mode.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/sm750fb/ddk750_mode.c b/drivers/staging/sm750fb/ddk750_mode.c
> index f3f354831617..bcdd291d25c9 100644
> --- a/drivers/staging/sm750fb/ddk750_mode.c
> +++ b/drivers/staging/sm750fb/ddk750_mode.c
> @@ -14,7 +14,7 @@
>    * in bit 29:27 of Display Control register.
>    */
>   static unsigned long
> -display_control_adjust_SM750LE(struct mode_parameter *mode_param,
> +display_control_adjust_sm750le(struct mode_parameter *mode_param,
>   			       unsigned long disp_control)
>   {
>   	unsigned long x, y;
> @@ -125,7 +125,7 @@ static int program_mode_registers(struct mode_parameter *mode_param,
>   			tmp |= DISPLAY_CTRL_HSYNC_PHASE;
>   
>   		if (sm750_get_chip_type() == SM750LE) {
> -			display_control_adjust_SM750LE(mode_param, tmp);
> +			display_control_adjust_sm750le(mode_param, tmp);
>   		} else {
>   			reg = peek32(CRT_DISPLAY_CTRL) &
>   				~(DISPLAY_CTRL_VSYNC_PHASE |

  reply	other threads:[~2023-10-18  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  8:04 [PATCH v2] Staging: sm750fb: Rename display_control_adjust_sm750LE Dorcas AnonoLitunya
2023-10-18  8:12 ` Karolina Stolarek [this message]
2023-10-18  9:31   ` Dan Carpenter
2023-10-18  8:26 ` 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=870b9b74-75bc-2a0d-7138-ae8df237f980@intel.com \
    --to=karolina.stolarek@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anonolitunya@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --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