From: Nam Cao <namcaov@gmail.com>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: outreachy@lists.linux.dev, greg@kroah.com,
forest@alittletooquiet.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: Fix Lines should not end with a '('
Date: Thu, 20 Oct 2022 13:10:56 +0200 [thread overview]
Message-ID: <20221020111056.GA168499@nam-dell> (raw)
In-Reply-To: <Y1EpYbkrau17uhDI@elroy-temp-vm.gaiao0uenmiufjlowqgp5yxwdh.gvxx.internal.cloudapp.net>
On Thu, Oct 20, 2022 at 10:56:33AM +0000, Tanjuate Brunostar wrote:
> Code style warnings reported by checkpatch.
> Improve the layout of a function header:
> Put the first parameter immediately after the '(' and align the other
> parameters underneath it.
>
> Signed-off-by: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
>
> ---
> v2: put static and void on the same line and adjusted the indentation as
> suggested by Greg KH
> ---
> drivers/staging/vt6655/rxtx.c | 18 ++++++------------
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> index 5bdb5176772c..d987f7dff02a 100644
> --- a/drivers/staging/vt6655/rxtx.c
> +++ b/drivers/staging/vt6655/rxtx.c
> @@ -85,10 +85,8 @@ static const unsigned short wFB_Opt1[2][5] = {
> #define DATADUR_A_F1 13
>
> /*--------------------- Static Functions --------------------------*/
> -static
> -void
> -s_vFillRTSHead(
> - struct vnt_private *pDevice,
> +static void
> +s_vFillRTSHead(struct vnt_private *pDevice,
> unsigned char byPktType,
> void *pvRTS,
> unsigned int cbFrameLength,
> @@ -96,13 +94,10 @@ s_vFillRTSHead(
> bool bDisCRC,
> struct ieee80211_hdr *hdr,
> unsigned short wCurrentRate,
> - unsigned char byFBOption
> -);
> + unsigned char byFBOption);
>
> -static
> -void
> -s_vGenerateTxParameter(
> - struct vnt_private *pDevice,
> +static void
> +s_vGenerateTxParameter(struct vnt_private *pDevice,
> unsigned char byPktType,
> struct vnt_tx_fifo_head *,
> void *pvRrvTime,
> @@ -112,8 +107,7 @@ s_vGenerateTxParameter(
> bool bNeedACK,
> unsigned int uDMAIdx,
> void *psEthHeader,
> - unsigned short wCurrentRate
> -);
> + unsigned short wCurrentRate);
>
> static unsigned int
> s_cbFillTxBufHead(struct vnt_private *pDevice, unsigned char byPktType,
> --
> 2.34.1
>
I think you mistakenly sent v2 again..
Best regards,
Nam
next prev parent reply other threads:[~2022-10-20 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:56 [PATCH v3] staging: vt6655: Fix Lines should not end with a '(' Tanjuate Brunostar
2022-10-20 11:10 ` Nam Cao [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-20 11:30 Tanjuate Brunostar
2022-10-20 15:00 ` Greg KH
2022-10-20 18:27 [PATCH 0/6] staging: vt6655: a series of checkpatch fixes on Tanjuate Brunostar
2022-10-20 18:27 ` [PATCH v3] staging: vt6655: Fix Lines should not end with a '(' Tanjuate 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=20221020111056.GA168499@nam-dell \
--to=namcaov@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=greg@kroah.com \
--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;
as well as URLs for NNTP newsgroup(s).