From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Punit Vara <punitvara@gmail.com>, jirislaby@gmail.com
Cc: mickflemm@gmail.com, mcgrof@do-not-panic.com,
kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 14/15] net: wireless: ath: Remove unneeded variable ret returning 0
Date: Thu, 22 Oct 2015 21:35:01 +0300 [thread overview]
Message-ID: <56292C55.4030706@cogentembedded.com> (raw)
In-Reply-To: <1445538363-2893-1-git-send-email-punitvara@gmail.com>
Hello.
On 10/22/2015 09:26 PM, Punit Vara wrote:
> This patch is to the ath5k/eeprom.c that fixes up warning caught by
> coccicheck:
>
> -Unneeded variable: "ret". Return "0" on line 1733
>
> Remove unneccesary variable ret created to return zero.
>
> Also removed empty line suggested by Sergei
>
> Signed-off-by: Punit Vara <punitvara@gmail.com>
> ---
> drivers/net/wireless/ath/ath5k/eeprom.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath5k/eeprom.c b/drivers/net/wireless/ath/ath5k/eeprom.c
> index 94d34ee..0c82ea5 100644
> --- a/drivers/net/wireless/ath/ath5k/eeprom.c
> +++ b/drivers/net/wireless/ath/ath5k/eeprom.c
> @@ -1707,8 +1707,7 @@ ath5k_eeprom_read_spur_chans(struct ath5k_hw *ah)
> struct ath5k_eeprom_info *ee = &ah->ah_capabilities.cap_eeprom;
> u32 offset;
> u16 val;
> - int ret = 0, i;
> -
No, this one shouldn't have been removed. There should an empty line
between the declarations and the statements.
> + int i;
> offset = AR5K_EEPROM_CTL(ee->ee_version) +
> AR5K_EEPROM_N_CTLS(ee->ee_version);
>
MBR, Sergei
next prev parent reply other threads:[~2015-10-22 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:26 [PATCH v3 14/15] net: wireless: ath: Remove unneeded variable ret returning 0 Punit Vara
2015-10-22 18:35 ` Sergei Shtylyov [this message]
2015-10-22 18:53 ` punit vara
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=56292C55.4030706@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=jirislaby@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mickflemm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=punitvara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.