From: Vinicius Peixoto <vpeixoto@lkcamp.dev>
To: Fabricio Gasperin <fgasperin@lkcamp.dev>,
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, ~lkcamp/patches@lists.sr.ht
Subject: Re: [PATCH] staging: sm750fb: Rename variable sm750_hw_cursor_setData2
Date: Sat, 21 Sep 2024 12:38:35 -0300 [thread overview]
Message-ID: <bf02d1e2-c912-4e43-9396-7e056d1b92ef@lkcamp.dev> (raw)
In-Reply-To: <20240921152124.11560-1-fgasperin@lkcamp.dev>
Hi Fabricio,
On 9/21/24 12:21, Fabricio Gasperin wrote:
> Rename function sm750_hw_cursor_setData2 to sm_750_hw_cursor_setdata2
>
> Change made in order to silence the camelCase warning from checkpatch.pl
>
> Signed-off-by: Fabricio Gasperin <fgasperin@lkcamp.dev>
> ---
> drivers/staging/sm750fb/sm750_cursor.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/sm750fb/sm750_cursor.c b/drivers/staging/sm750fb/sm750_cursor.c
> index eea4d1bd36ce..e95f39b51a2f 100644
> --- a/drivers/staging/sm750fb/sm750_cursor.c
> +++ b/drivers/staging/sm750fb/sm750_cursor.c
> @@ -131,7 +131,7 @@ void sm750_hw_cursor_setData(struct lynx_cursor *cursor, u16 rop,
> }
> }
>
> -void sm750_hw_cursor_setData2(struct lynx_cursor *cursor, u16 rop,
> +void sm750_hw_cursor_setdata2(struct lynx_cursor *cursor, u16 rop,
> const u8 *pcol, const u8 *pmsk)
I think you missed one other occurrence of this function in the header
(drivers/staging/sm750fb/sm750_cursor.h), which causes it to fail to
build. Please fix the function name there as well. I think those are the
only two occurrences of it, though.
> {
> int i, j, count, pitch, offset;
Thanks,
Vinicius
next prev parent reply other threads:[~2024-09-21 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 15:21 Fabricio Gasperin
2024-09-21 15:38 ` Vinicius Peixoto [this message]
2024-09-21 23:49 ` kernel test robot
2024-09-22 2:15 ` kernel test robot
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=bf02d1e2-c912-4e43-9396-7e056d1b92ef@lkcamp.dev \
--to=vpeixoto@lkcamp.dev \
--cc=fgasperin@lkcamp.dev \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=~lkcamp/patches@lists.sr.ht \
/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
all inboxes | Powered by JetHome®