From: Pavel Skripkin <paskripkin@gmail.com>
To: Michael Straube <straube.linux@gmail.com>, gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] staging: r8188eu: IntArray and C2hArray are set but never used
Date: Thu, 30 Dec 2021 23:11:10 +0300 [thread overview]
Message-ID: <2838d56e-9618-1582-4127-9dc3d56ff311@gmail.com> (raw)
In-Reply-To: <20211230200059.13406-7-straube.linux@gmail.com>
On 12/30/21 23:00, Michael Straube wrote:
> The fields IntArray and C2hArray of struct hal_data_8188e are set but
> never used. Remove them.
>
> While at it, remove the unsed defines USB_INTR_CONTENT_CPWM1_OFFSET
> and USB_INTR_CONTENT_CPWM2_OFFSET as well.
>
> Signed-off-by: Michael Straube <straube.linux@gmail.com>
> ---
Hi Michael,
thanks for your clean ups!
> drivers/staging/r8188eu/hal/usb_ops_linux.c | 10 ----------
> drivers/staging/r8188eu/include/rtl8188e_hal.h | 3 ---
> drivers/staging/r8188eu/include/rtl8188e_spec.h | 7 -------
> 3 files changed, 20 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/hal/usb_ops_linux.c b/drivers/staging/r8188eu/hal/usb_ops_linux.c
> index 9ec55a77dccd..85bcde5ee79a 100644
> --- a/drivers/staging/r8188eu/hal/usb_ops_linux.c
> +++ b/drivers/staging/r8188eu/hal/usb_ops_linux.c
> @@ -185,20 +185,10 @@ int rtw_writeN(struct adapter *adapter, u32 addr, u32 length, u8 *data)
>
> static void interrupt_handler_8188eu(struct adapter *adapt, u16 pkt_len, u8 *pbuf)
> {
> - struct hal_data_8188e *haldata = &adapt->haldata;
> -
> if (pkt_len != INTERRUPT_MSG_FORMAT_LEN) {
> DBG_88E("%s Invalid interrupt content length (%d)!\n", __func__, pkt_len);
> return;
> }
> -
> - /* HISR */
> - memcpy(&haldata->IntArray[0], &pbuf[USB_INTR_CONTENT_HISR_OFFSET], 4);
> - memcpy(&haldata->IntArray[1], &pbuf[USB_INTR_CONTENT_HISRE_OFFSET], 4);
> -
> - /* C2H Event */
> - if (pbuf[0] != 0)
> - memcpy(&haldata->C2hArray[0], &pbuf[USB_INTR_CONTENT_C2H_OFFSET], 16);
> }
>
This function can be removed totally then, since it does nothing. Not
sure if function removal fits this patch, but why not :)
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-12-30 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 20:00 [PATCH 0/7] staging: r8188eu: clean up struct hal_data_r8188e Michael Straube
2021-12-30 20:00 ` [PATCH 1/7] staging: r8188eu: bRDGEnable is always false Michael Straube
2021-12-30 20:00 ` [PATCH 2/7] staging: r8188eu: UsbRxHighSpeedMode is set but never used Michael Straube
2021-12-30 20:00 ` [PATCH 3/7] staging: r8188eu: bTXPowerDataReadFromEEPORM " Michael Straube
2021-12-30 20:00 ` [PATCH 4/7] staging: r8188eu: bAPKThermalMeterIgnore " Michael Straube
2021-12-30 20:00 ` [PATCH 5/7] staging: r8188eu: remove unused fields from struct hal_data_8188e Michael Straube
2021-12-30 20:00 ` [PATCH 6/7] staging: r8188eu: IntArray and C2hArray are set but never used Michael Straube
2021-12-30 20:11 ` Pavel Skripkin [this message]
2022-01-01 8:21 ` Michael Straube
2021-12-30 20:00 ` [PATCH 7/7] staging: r8188eu: FwRsvdPageStartOffset is " Michael Straube
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=2838d56e-9618-1582-4127-9dc3d56ff311@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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
all inboxes | Powered by JetHome®