linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KY Srinivasan <kys@microsoft.com>
To: David Binderman <dcb314@hotmail.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: linux-4.18-rc8/tools/hv/hv_kvp_daemon.c:289: dead code block ?
Date: Mon, 6 Aug 2018 15:28:03 +0000	[thread overview]
Message-ID: <MW2PR2101MB1113A4A2F965646EDF1FEF02A0200@MW2PR2101MB1113.namprd21.prod.outlook.com> (raw)
In-Reply-To: <VI1PR08MB3342B5316CD432BB985E1A5D9C200@VI1PR08MB3342.eurprd08.prod.outlook.com>



> -----Original Message-----
> From: David Binderman <dcb314@hotmail.com>
> Sent: Monday, August 6, 2018 1:08 AM
> To: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> <haiyangz@microsoft.com>; Stephen Hemminger
> <sthemmin@microsoft.com>; devel@linuxdriverproject.org; linux-
> kernel@vger.kernel.org
> Subject: linux-4.18-rc8/tools/hv/hv_kvp_daemon.c:289: dead code block ?
> 
> 
> Hello there,
> 
> linux-4.18-rc8/tools/hv/hv_kvp_daemon.c:282] -> [linux-4.18-
> rc8/tools/hv/hv_kvp_daemon.c:289]: (warning) Opposite inner 'if' condition
> leads to a dead code block.
> 
> Source code is
> 
>        for (i = 0; i < num_records; i++) {
>                 if (memcmp(key, record[i].key, key_size))
>                         continue;
>                 /*
>                  * Found a match; just move the remaining
>                  * entries up.
>                  */
>                 if (i == num_records) {

Thank you! We will fix the issue.

K. Y
> 
> Regards
> 
> David Binderman

           reply	other threads:[~2018-08-06 15:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <VI1PR08MB3342B5316CD432BB985E1A5D9C200@VI1PR08MB3342.eurprd08.prod.outlook.com>]

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=MW2PR2101MB1113A4A2F965646EDF1FEF02A0200@MW2PR2101MB1113.namprd21.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=dcb314@hotmail.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthemmin@microsoft.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;
as well as URLs for NNTP newsgroup(s).