From: Johannes Berg <johannes@sipsolutions.net>
To: baomingtong001@208suo.com, kvalo@kernel.org
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: ath9k: remove unneeded variable from ath9k_dump_legacy_btcoex()
Date: Wed, 14 Jun 2023 09:38:15 +0200 [thread overview]
Message-ID: <02650a6d4c82bce62a9625714540ea75f7b3f571.camel@sipsolutions.net> (raw)
In-Reply-To: <695b68601eecd648b7531f2e40561edb@208suo.com>
On Wed, 2023-06-14 at 14:13 +0800, baomingtong001@208suo.com wrote:
> Fix the following coccicheck warning:
>
> drivers/net/wireless/ath/ath9k/gpio.c:501:5-8: Unneeded variable: "len".
>
> Signed-off-by: Mingtong Bao <baomingtong001@208suo.com>
Same here. I'm even wondering if there are different people behind this?
Also, I'm wondering what you're up to - are you all training or
something? I see the same kind of patches that are the same kind of
broken from a handful of different people?
> ---
> drivers/net/wireless/ath/ath9k/gpio.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/gpio.c
> b/drivers/net/wireless/ath/ath9k/gpio.c
> index b457e52dd365..f3d1bc02e633 100644
> --- a/drivers/net/wireless/ath/ath9k/gpio.c
> +++ b/drivers/net/wireless/ath/ath9k/gpio.c
> @@ -498,14 +498,13 @@ static int ath9k_dump_legacy_btcoex(struct
> ath_softc *sc, u8 *buf, u32 size)
> {
>
> struct ath_btcoex *btcoex = &sc->btcoex;
> - u32 len = 0;
>
> ATH_DUMP_BTCOEX("Stomp Type", btcoex->bt_stomp_type);
> ATH_DUMP_BTCOEX("BTCoex Period (msec)", btcoex->btcoex_period);
> ATH_DUMP_BTCOEX("Duty Cycle", btcoex->duty_cycle);
> ATH_DUMP_BTCOEX("BT Wait time", btcoex->bt_wait_time);
>
> - return len;
> + return 0;
>
This won't even build.
Please try to understand the code you're modifying before you do. And
no, build-testing it (and fixing it) will not result anything better.
johannes
prev parent reply other threads:[~2023-06-14 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614061007.62077-1-luojianhong@cdjrlc.com>
2023-06-14 6:13 ` baomingtong001
2023-06-14 7:38 ` Johannes Berg [this message]
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=02650a6d4c82bce62a9625714540ea75f7b3f571.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=baomingtong001@208suo.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®