From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: Michal Kobylinski <michalx.kobylinski@intel.com>,
john.mcnamara@intel.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] examples/netmap_compat: fix infinite loop
Date: Mon, 16 May 2016 18:54:44 +0200 [thread overview]
Message-ID: <5229237.mgEh5IYliP@xps13> (raw)
In-Reply-To: <1461763361-9054-1-git-send-email-michalx.kobylinski@intel.com>
2016-04-27 15:22, Michal Kobylinski:
> Fix issue reported by Coverity.
>
> Coverity ID 30701: Infinite loop: The loop does not have a normal
> termination condition, so will continue until an abnormal condition
> arises. In rte_netmap_poll: Infinite loop with unsatisfiable exit
> condition.
>
> Fixes: 06371afe394d ("examples/netmap_compat: import netmap
> compatibility example")
>
> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-05-16 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 10:47 [dpdk-dev] [PATCH] " Michal Kobylinski
2016-04-22 11:51 ` Mcnamara, John
2016-04-27 13:22 ` [dpdk-dev] [PATCH v2] " Michal Kobylinski
2016-05-16 16:54 ` Thomas Monjalon [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=5229237.mgEh5IYliP@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=michalx.kobylinski@intel.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).