From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH v3 1/6] staging: vt6655: fix lines ending in a '('
Date: Sat, 22 Oct 2022 10:10:16 +0200 [thread overview]
Message-ID: <Y1OlaBVGgHvAipuB@kroah.com> (raw)
In-Reply-To: <20221022070612.13009-2-tanjubrunostar0@gmail.com>
On Sat, Oct 22, 2022 at 07:06:07AM +0000, Tanjuate Brunostar wrote:
> fix serveral checkpatch errors related to lines ending with a '(' by
> refactoring the code lines
>
> Signed-off-by: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
> ---
> drivers/staging/vt6655/rxtx.c | 149 ++++++++++++++--------------------
> 1 file changed, 63 insertions(+), 86 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> index 1e5036121665..f9d0b00d7cff 100644
> --- a/drivers/staging/vt6655/rxtx.c
> +++ b/drivers/staging/vt6655/rxtx.c
> @@ -141,13 +141,11 @@ static __le16 vnt_time_stamp_off(struct vnt_private *priv, u16 rate)
> */
> static
> unsigned int
> -s_uGetTxRsvTime(
> - struct vnt_private *pDevice,
> - unsigned char byPktType,
> - unsigned int cbFrameLength,
> - unsigned short wRate,
> - bool bNeedAck
> -)
> +s_uGetTxRsvTime(struct vnt_private *pDevice,
You have a strange mix of choices here for how you changed the code.
This time you did not move the "static" or "unsigned int" to the same
line as the function name, but then:
> + unsigned char byPktType,
> + unsigned int cbFrameLength,
> + unsigned short wRate,
> + bool bNeedAck)
> {
> unsigned int uDataTime, uAckTime;
>
> @@ -215,19 +213,16 @@ static __le16 get_rtscts_time(struct vnt_private *priv,
>
> /* byFreqType 0: 5GHz, 1:2.4Ghz */
> static
> -unsigned int
> -s_uGetDataDuration(
> - struct vnt_private *pDevice,
> - unsigned char byDurType,
> - unsigned int cbFrameLength,
> - unsigned char byPktType,
> - unsigned short wRate,
> - bool bNeedAck,
> - unsigned int uFragIdx,
> - unsigned int cbLastFragmentSize,
> - unsigned int uMACfragNum,
> - unsigned char byFBOption
> -)
> +unsigned int s_uGetDataDuration(struct vnt_private *pDevice,
You moved "unsigned int" here, but then:
> + unsigned char byDurType,
> + unsigned int cbFrameLength,
> + unsigned char byPktType,
> + unsigned short wRate,
> + bool bNeedAck,
> + unsigned int uFragIdx,
> + unsigned int cbLastFragmentSize,
> + unsigned int uMACfragNum,
> + unsigned char byFBOption)
> {
> bool bLastFrag = false;
> unsigned int uAckTime = 0, uNextPktTime = 0, len;
> @@ -316,17 +311,13 @@ s_uGetDataDuration(
> }
>
> /* byFreqType: 0=>5GHZ 1=>2.4GHZ */
> -static
> -__le16
> -s_uGetRTSCTSDuration(
> - struct vnt_private *pDevice,
> - unsigned char byDurType,
> - unsigned int cbFrameLength,
> - unsigned char byPktType,
> - unsigned short wRate,
> - bool bNeedAck,
> - unsigned char byFBOption
> -)
> +static __le16 s_uGetRTSCTSDuration(struct vnt_private *pDevice,
You did both the static and the return type here.
Pick one style and stick with it please. Consistancy matters, that is
why we have a coding style to start with. Brains and pattern matching
and all that.
In this case, this last one (both static and the return type), should be
used.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-22 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 7:06 [PATCH v3 0/6] a series of checkpatch fixes on the file: rxtx.c Tanjuate Brunostar
2022-10-22 7:06 ` [PATCH v3 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-22 7:18 ` Joe Perches
2022-10-22 7:35 ` Tanju Brunostar
2022-10-22 8:10 ` Greg KH [this message]
2022-10-22 8:24 ` Tanju Brunostar
2022-10-22 7:06 ` [PATCH v3 2/6] staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-22 8:11 ` Greg KH
2022-10-22 8:26 ` Tanju Brunostar
2022-10-22 7:06 ` [PATCH v3 3/6] staging: vt6655: refactor long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-22 8:12 ` Greg KH
2022-10-22 8:27 ` Tanju Brunostar
2022-10-22 7:06 ` [PATCH v3 4/6] staging: vt6655: refactor long lines of code in s_vGenerateTxParameter Tanjuate Brunostar
2022-10-22 8:14 ` Greg KH
2022-10-22 8:28 ` Tanju Brunostar
2022-10-22 7:06 ` [PATCH v3 5/6] staging: vt6655: refactor long lines of code in the rest of the file Tanjuate Brunostar
2022-10-22 8:14 ` Greg KH
2022-10-22 8:29 ` Tanju Brunostar
2022-10-22 7:06 ` [PATCH v3 6/6] staging: vt6655: refactor code to avoid a line ending in '(' Tanjuate Brunostar
2022-10-22 7:35 ` [PATCH v3 0/6] a series of checkpatch fixes on the file: rxtx.c Greg KH
2022-10-22 8:22 ` Tanju Brunostar
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=Y1OlaBVGgHvAipuB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@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