From: Julia Lawall <julia.lawall@inria.fr>
To: aliya-rahmani <aliyarahmani786@gmail.com>
Cc: tomm.merciai@gmail.com, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: vt6655f: rxtx: code style - Fix Lines should not end with a '('
Date: Wed, 13 Apr 2022 11:06:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204131104030.3470@hadrien> (raw)
In-Reply-To: <20220413073545.14666-1-aliyarahmani786@gmail.com>
On Wed, 13 Apr 2022, aliya-rahmani wrote:
> From: Aliya Rahmani <aliyarahmani786@gmail.com>
>
> Removed indentation to fix the checkpatch error that lines should not
> end with a '('.
The log message should be in the imperative, so it would be "Remove", not
"Removed".
Maybe it would be nice to keep the parameters aligned, thus indent the
others more?
In another patch you could improve the variable names and the function
name. I'm not sure why static and void have to be on separate lines
either.
julia
>
> Signed-off-by: Aliya Rahmani <aliyarahmani786@gmail.com>
>
> ---
> drivers/staging/vt6655/rxtx.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> index 53506e242a96..dce9d87d2363 100644
> --- a/drivers/staging/vt6655/rxtx.c
> +++ b/drivers/staging/vt6655/rxtx.c
> @@ -569,8 +569,7 @@ s_uFillDataHead(
>
> static
> void
> -s_vFillRTSHead(
> - struct vnt_private *pDevice,
> +s_vFillRTSHead(struct vnt_private *pDevice,
> unsigned char byPktType,
> void *pvRTS,
> unsigned int cbFrameLength,
> --
> 2.25.1
>
>
>
prev parent reply other threads:[~2022-04-13 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:35 [PATCH] staging: vt6655f: rxtx: code style - Fix Lines should not end with a '(' aliya-rahmani
2022-04-13 7:51 ` Dan Carpenter
2022-04-13 9:06 ` Julia Lawall [this message]
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=alpine.DEB.2.22.394.2204131104030.3470@hadrien \
--to=julia.lawall@inria.fr \
--cc=aliyarahmani786@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tomm.merciai@gmail.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