DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, ChangqingX" <changqingx.wu@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/ipsec: fix compile error on BSD
Date: Thu, 17 Jan 2019 01:18:41 +0000	[thread overview]
Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B690494@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1547646341-17346-1-git-send-email-bernard.iremonger@intel.com>

Tested-by: Wu, ChangqingX <changqingx.wu@intel.com>

-----Original Message-----
From: Iremonger, Bernard 
Sent: Wednesday, January 16, 2019 9:46 PM
To: dev@dpdk.org; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Wu, ChangqingX <changqingx.wu@intel.com>
Cc: Iremonger, Bernard <bernard.iremonger@intel.com>
Subject: [PATCH] test/ipsec: fix compile error on BSD

Removed ip.h and in.h headers to fix unknown type errors when compiling on BSD.

Fixes: 05fe65eb66b2 ("test/ipsec: introduce functional test")
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
 test/test/test_ipsec.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/test/test/test_ipsec.c b/test/test/test_ipsec.c index ff1a1c4..f49c8d8 100644
--- a/test/test/test_ipsec.c
+++ b/test/test/test_ipsec.c
@@ -4,9 +4,6 @@
 
 #include <time.h>
 
-#include <netinet/in.h>
-#include <netinet/ip.h>
-
 #include <rte_common.h>
 #include <rte_hexdump.h>
 #include <rte_mbuf.h>
--
2.7.4

      parent reply	other threads:[~2019-01-17  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 13:45 Bernard Iremonger
2019-01-16 14:01 ` Ananyev, Konstantin
2019-01-17  1:17   ` Wu, ChangqingX
2019-01-17 23:25   ` Thomas Monjalon
2019-01-17  1:18 ` Wu, ChangqingX [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=7F81DD3887C58F49A6B2EFEC3C28E22E0B690494@SHSMSX101.ccr.corp.intel.com \
    --to=changqingx.wu@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).