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 5/6] staging: vt6655: refactor long lines of code in the rest of the file
Date: Sat, 22 Oct 2022 10:14:59 +0200 [thread overview]
Message-ID: <Y1Omg6Tfv/lc7Fu4@kroah.com> (raw)
In-Reply-To: <20221022070612.13009-6-tanjubrunostar0@gmail.com>
On Sat, Oct 22, 2022 at 07:06:11AM +0000, Tanjuate Brunostar wrote:
> fix checkpatch errors by refactoring long lines of code in the rest of
> the file
>
> Signed-off-by: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
> ---
> drivers/staging/vt6655/rxtx.c | 105 ++++++++++++++++++++++------------
> 1 file changed, 67 insertions(+), 38 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> index 951d4172e9f2..572be45cdbeb 100644
> --- a/drivers/staging/vt6655/rxtx.c
> +++ b/drivers/staging/vt6655/rxtx.c
> @@ -1105,44 +1105,60 @@ s_cbFillTxBufHead(struct vnt_private *pDevice, unsigned char byPktType,
> if (byFBOption == AUTO_FB_NONE) {
> if (bRTS) {/* RTS_need */
> pvRrvTime = (void *)(pbyTxBufferAddr + wTxBufSize);
> - pMICHDR = (struct vnt_mic_hdr *)(pbyTxBufferAddr + wTxBufSize + sizeof(struct vnt_rrv_time_rts));
> - pvRTS = (void *)(pbyTxBufferAddr + wTxBufSize + sizeof(struct vnt_rrv_time_rts) + cbMICHDR);
> + pMICHDR = (struct vnt_mic_hdr *)(pbyTxBufferAddr + wTxBufSize +
> + sizeof(struct vnt_rrv_time_rts));
> + pvRTS = (void *)(pbyTxBufferAddr + wTxBufSize +
> + sizeof(struct vnt_rrv_time_rts) + cbMICHDR);
Casting to void * is very odd. Try working on fixing up that mess
first...
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
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 [this message]
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=Y1Omg6Tfv/lc7Fu4@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