From: Jakub Kicinski <kubakici@wp.pl>
To: Colin King <colin.king@canonical.com>
Cc: Lino Sanfilippo <LinoSanfilippo@gmx.de>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: slicoss: remove redundant initialization of idx
Date: Mon, 30 Oct 2017 18:04:49 +0000 [thread overview]
Message-ID: <20171030110449.3aea9670@cakuba.netronome.com> (raw)
In-Reply-To: <20171029133809.6831-1-colin.king@canonical.com>
On Sun, 29 Oct 2017 13:38:09 +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable idx is being initialized and later on over-written by
> a new value in a do-loop without the initial value ever being
> read. Hence the initializion is redundant and can be removed.
> Cleans up clang warning:
>
> drivers/net/ethernet/alacritech/slicoss.c:358:15: warning: Value
> stored to 'idx' during its initialization is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/net/ethernet/alacritech/slicoss.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/alacritech/slicoss.c b/drivers/net/ethernet/alacritech/slicoss.c
> index 15a8096c60df..ac8004186fa8 100644
> --- a/drivers/net/ethernet/alacritech/slicoss.c
> +++ b/drivers/net/ethernet/alacritech/slicoss.c
> @@ -355,7 +355,7 @@ static void slic_xmit_complete(struct slic_device *sdev)
> {
> struct slic_tx_queue *txq = &sdev->txq;
> struct net_device *dev = sdev->netdev;
> - unsigned int idx = txq->done_idx;
> + unsigned int idx;
> struct slic_tx_buffer *buff;
> unsigned int frames = 0;
> unsigned int bytes = 0;
You should probably reorder the variables now so they stay longest to
shortest.
next prev parent reply other threads:[~2017-10-30 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 13:38 [PATCH] net: ethernet: slicoss: remove redundant initialization of idx Colin King
2017-10-30 17:36 ` Lino Sanfilippo
2017-10-30 18:04 ` Jakub Kicinski [this message]
2017-10-30 18:23 ` Lino Sanfilippo
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=20171030110449.3aea9670@cakuba.netronome.com \
--to=kubakici@wp.pl \
--cc=LinoSanfilippo@gmx.de \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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