From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, Rami Rosen <ramirose@gmail.com>, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix unreachable code
Date: Mon, 22 Apr 2019 23:05:35 +0200 [thread overview]
Message-ID: <2524354.HtNxz6UQSK@xps> (raw)
Message-ID: <20190422210535.08x1hjBp-vyxFEB4zANfktm_D5euMpwdn-Q65407FRM@z> (raw)
In-Reply-To: <CAHLOa7TDi1yQdL6YTNkz1Qsn-ESALYtxEorg-EqjMw+NO=tnYw@mail.gmail.com>
> > A for loop to MAX_VFS had a break as the last line, so the w++
> > would never get called, breaking out of the loop after the
> > first iteration. Remove the break so that the loop can execute
> > properly.
> >
> > Fixes: ace158c4a821 ("examples/vm_power: add check for port count")
> > Coverity issue: 337682
> >
> > Signed-off-by: David Hunt <david.hunt@intel.com>
>
> Acked-by: Rami Rosen <ramirose@gmail.com>
Applied, thanks
next prev parent reply other threads:[~2019-04-22 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 13:13 David Hunt
2019-04-10 13:13 ` David Hunt
2019-04-10 23:58 ` Rami Rosen
2019-04-10 23:58 ` Rami Rosen
2019-04-22 21:05 ` Thomas Monjalon [this message]
2019-04-22 21:05 ` Thomas Monjalon
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=2524354.HtNxz6UQSK@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).