From: Kloudifold <cloudifold.3125@gmail.com>
To: julia.lawall@inria.fr
Cc: teddy.wang@siliconmotion.com, sudipm.mukherjee@gmail.com,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750: Rename camel case functions in sm750_cursor.*
Date: Sat, 11 Mar 2023 05:47:34 +0800 [thread overview]
Message-ID: <ZAuldn536Ci0fcrV@CloudiRingWorld> (raw)
Thank you for your advice! Should I change this patch and patch message
and resend it?
On Sat, 11 Mar 2023 at 05:39, Julia Lawall <julia.lawall@inria.fr> wrote:
>
> You don't need the filename in the subject.
>
> On Sat, 11 Mar 2023, Kloudifold wrote:
>
> > This patch fixes the "CHECK: Avoid CamelCase" reported by
> > checkpatch.pl by renaming camel case functions.
> >
> > Signed-off-by: Kloudifold <cloudifold.3125@gmail.com>
> > ---
> > drivers/staging/sm750fb/sm750_cursor.c | 14 +++++++-------
> > drivers/staging/sm750fb/sm750_cursor.h | 12 ++++++------
> > 2 files changed, 13 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/staging/sm750fb/sm750_cursor.c b/drivers/staging/sm750fb/sm750_cursor.c
> > index 43e6f52c2..ff643e33f 100644
> > --- a/drivers/staging/sm750fb/sm750_cursor.c
> > +++ b/drivers/staging/sm750fb/sm750_cursor.c
> > @@ -58,13 +58,13 @@ void sm750_hw_cursor_disable(struct lynx_cursor *cursor)
> > poke32(HWC_ADDRESS, 0);
> > }
> >
> > -void sm750_hw_cursor_setSize(struct lynx_cursor *cursor, int w, int h)
> > +void sm750_hw_cursor_set_size(struct lynx_cursor *cursor, int w, int h)
> > {
> > cursor->w = w;
> > cursor->h = h;
> > }
> >
> > -void sm750_hw_cursor_setPos(struct lynx_cursor *cursor, int x, int y)
> > +void sm750_hw_cursor_set_pos(struct lynx_cursor *cursor, int x, int y)
> > {
> > u32 reg;
> >
> > @@ -73,7 +73,7 @@ void sm750_hw_cursor_setPos(struct lynx_cursor *cursor, int x, int y)
> > poke32(HWC_LOCATION, reg);
> > }
> >
> > -void sm750_hw_cursor_setColor(struct lynx_cursor *cursor, u32 fg, u32 bg)
> > +void sm750_hw_cursor_set_color(struct lynx_cursor *cursor, u32 fg, u32 bg)
> > {
> > u32 reg = (fg << HWC_COLOR_12_2_RGB565_SHIFT) &
> > HWC_COLOR_12_2_RGB565_MASK;
> > @@ -82,8 +82,8 @@ void sm750_hw_cursor_setColor(struct lynx_cursor *cursor, u32 fg, u32 bg)
> > poke32(HWC_COLOR_3, 0xffe0);
> > }
> >
> > -void sm750_hw_cursor_setData(struct lynx_cursor *cursor, u16 rop,
> > - const u8 *pcol, const u8 *pmsk)
> > +void sm750_hw_cursor_set_data(struct lynx_cursor *cursor, u16 rop,
> > + const u8 *pcol, const u8 *pmsk)
>
> The indentation of the second line looks random. It's not a multiple of
> the tabs, and it doesn't line up with the right side of the (. So there
> doesn't seem to be any need to change it for this patch.
next reply other threads:[~2023-03-10 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 21:47 Kloudifold [this message]
2023-03-10 21:52 ` [PATCH] staging: sm750: Rename camel case functions in sm750_cursor.* Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 22:23 Kloudifold
2023-03-11 8:53 ` Julia Lawall
2023-03-10 21:33 Kloudifold
2023-03-10 21:39 ` Julia Lawall
2023-03-11 1:06 ` kernel test robot
2023-03-13 0:38 ` Ira Weiny
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=ZAuldn536Ci0fcrV@CloudiRingWorld \
--to=cloudifold.3125@gmail.com \
--cc=alpine.DEB.2.22.394.2303102236190.3199@hadrien \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--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