From: Tom Rix <trix@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>, Nam Cao <namcaov@gmail.com>
Cc: nathan@kernel.org, ndesaulniers@google.com,
artur.bujdoso@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: remove unused pHalData variable
Date: Sun, 26 Mar 2023 06:13:16 -0700 [thread overview]
Message-ID: <8a2746a0-57e0-621b-7db9-2719554d050b@redhat.com> (raw)
In-Reply-To: <ZCBArurFCc7Pae+T@kroah.com>
On 3/26/23 5:55 AM, Greg KH wrote:
> On Sun, Mar 26, 2023 at 02:46:52PM +0200, Nam Cao wrote:
>> On Sun, Mar 26, 2023 at 08:23:21AM -0400, Tom Rix wrote:
>>> clang with W=1 reports
>>> drivers/staging/rtl8723bs/hal/hal_btcoex.c:1182:23: error: variable
>>> 'pHalData' set but not used [-Werror,-Wunused-but-set-variable]
>>> struct hal_com_data *pHalData;
>>> ^
>>> This variable is not used so remove it.
>>>
>>> Signed-off-by: Tom Rix <trix@redhat.com>
>>> ---
>>> drivers/staging/rtl8723bs/hal/hal_btcoex.c | 4 ----
>>> 1 file changed, 4 deletions(-)
>>>
>>> diff --git a/drivers/staging/rtl8723bs/hal/hal_btcoex.c b/drivers/staging/rtl8723bs/hal/hal_btcoex.c
>>> index e36f8c369a04..0cb2adcc1f78 100644
>>> --- a/drivers/staging/rtl8723bs/hal/hal_btcoex.c
>>> +++ b/drivers/staging/rtl8723bs/hal/hal_btcoex.c
>>> @@ -1179,10 +1179,6 @@ bool hal_btcoex_IsBtDisabled(struct adapter *padapter)
>>>
>>> void hal_btcoex_SetChipType(struct adapter *padapter, u8 chipType)
>>> {
>>> - struct hal_com_data *pHalData;
>>> -
>>> -
>>> - pHalData = GET_HAL_DATA(padapter);
>>> }
>> If this function doesn't do anything, does it not make more sense to
>> just remove this function entirely?
> This function is already removed in linux-next, so it doesn't matter :)
My patch is against linux-next from tag next-20230324
Tom
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2023-03-26 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 12:23 Tom Rix
2023-03-26 12:46 ` Nam Cao
2023-03-26 12:55 ` Greg KH
2023-03-26 13:13 ` Tom Rix [this message]
2023-03-26 13:20 ` Greg KH
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=8a2746a0-57e0-621b-7db9-2719554d050b@redhat.com \
--to=trix@redhat.com \
--cc=artur.bujdoso@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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®