From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] examples/ip_pipeline: fix configuration parser
Date: Mon, 14 Mar 2016 12:22:02 +0000 [thread overview]
Message-ID: <1457958122-20136-2-git-send-email-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <1457958122-20136-1-git-send-email-roy.fan.zhang@intel.com>
Fixes: 377cd98e ("example/ip_pipeline: add link identification")
Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
examples/ip_pipeline/config_parse.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/examples/ip_pipeline/config_parse.c b/examples/ip_pipeline/config_parse.c
index e39c23e..152889d 100644
--- a/examples/ip_pipeline/config_parse.c
+++ b/examples/ip_pipeline/config_parse.c
@@ -678,6 +678,8 @@ parse_eal(struct app_params *app,
p->pci_blacklist[i] =
strdup(entry->value);
PARSE_ERROR_MALLOC(p->pci_blacklist[i]);
+
+ break;
}
PARSE_ERROR_MESSAGE((i < APP_MAX_LINKS),
@@ -702,6 +704,8 @@ parse_eal(struct app_params *app,
p->pci_whitelist[i] = strdup(entry->value);
PARSE_ERROR_MALLOC(p->pci_whitelist[i]);
+
+ break;
}
PARSE_ERROR_MESSAGE((i < APP_MAX_LINKS),
@@ -720,6 +724,8 @@ parse_eal(struct app_params *app,
p->vdev[i] = strdup(entry->value);
PARSE_ERROR_MALLOC(p->vdev[i]);
+
+ break;
}
PARSE_ERROR_MESSAGE((i < APP_MAX_LINKS),
--
2.5.0
next prev parent reply other threads:[~2016-03-14 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 12:22 [dpdk-dev] [PATCH] app/test/test_table_acl: fix incorrect IP header Fan Zhang
2016-03-14 12:22 ` Fan Zhang [this message]
2016-03-22 18:16 ` [dpdk-dev] [PATCH] examples/ip_pipeline: fix configuration parser Thomas Monjalon
2016-03-16 20:30 ` [dpdk-dev] [PATCH] app/test/test_table_acl: fix incorrect IP header Thomas Monjalon
2016-03-25 11:59 ` Zhang, Roy Fan
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=1457958122-20136-2-git-send-email-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@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).