From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rxrpc: remove redundant initialization of variable 'len'
Date: Fri, 16 Mar 2018 09:49:28 -0400 (EDT) [thread overview]
Message-ID: <20180316.094928.699803274284942791.davem@davemloft.net> (raw)
In-Reply-To: <20180312172538.31707-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Mon, 12 Mar 2018 17:25:38 +0000
> From: Colin Ian King <colin.king@canonical.com>
>
> The variable 'len' is being initialized with a value that is never
> read and it is re-assigned later, hence the initialization is redundant
> and can be removed.
>
> Cleans up clang warning:
> net/rxrpc/recvmsg.c:275:15: warning: Value stored to 'len' during its
> initialization is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Hehe, if the diff provided just 2 more lines of context at the bottom
we'd be able to see the overriding assignment :-)
> @@ -272,7 +272,7 @@ static int rxrpc_locate_data(struct rxrpc_call *call, struct sk_buff *skb,
> unsigned int *_offset, unsigned int *_len)
> {
> unsigned int offset = sizeof(struct rxrpc_wire_header);
> - unsigned int len = *_len;
> + unsigned int len;
> int ret;
> u8 annotation = *_annotation;
>
> --
> 2.15.1
>
Applied, thanks Colin.
prev parent reply other threads:[~2018-03-16 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 17:25 [PATCH] rxrpc: remove redundant initialization of variable 'len' Colin King
2018-03-16 13:49 ` David Miller [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=20180316.094928.699803274284942791.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-afs@lists.infradead.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