DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: check error conditinos for every loop iteration
Date: Fri, 18 Apr 2014 00:26:56 +0200	[thread overview]
Message-ID: <2364421.nEfYD68tnk@xps13> (raw)
In-Reply-To: <1397645440-14813-1-git-send-email-nhorman@tuxdriver.com>

2014-04-16 06:50, Neil Horman:
> The return code for rte_cpu_get_flag_enabled is only checked on the
> termination of the for loop that it is called inside, but should be checked
> for every iteration it makes through the for loop.  This is caused by some
> silly missing brackets.  Simply add them in
> 
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> Reported-by: Pablo De Lara Guarch  <pablo.de.lara.guarch@intel.com>

Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>

It's applied for version 1.6.0r2.
Title is changed: "eal: fix check of all requested CPU features"

Thanks to all for reporting and fixing.
-- 
Thomas

      reply	other threads:[~2014-04-17 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 10:50 Neil Horman
2014-04-17 22:26 ` 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=2364421.nEfYD68tnk@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).