From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples: remove useless checking
Date: Mon, 16 May 2016 21:02:41 +0200 [thread overview]
Message-ID: <1788766.A9NIFKQcY4@xps13> (raw)
In-Reply-To: <5729AD0F.4060302@intel.com>
> > The rte_eth_dev_count() function will never return a value greater
> > than RTE_MAX_ETHPORTS, so that checking is useless.
> >
> > Signed-off-by: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-05-16 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 15:48 [dpdk-dev] [PATCH] " Mauricio Vasquez B
2016-05-03 14:39 ` Ferruh Yigit
2016-05-03 21:16 ` [dpdk-dev] [PATCH v2] " Mauricio Vasquez B
2016-05-04 8:04 ` Ferruh Yigit
2016-05-16 19:02 ` 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=1788766.A9NIFKQcY4@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mauricio.vasquezbernal@studenti.polito.it \
/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).