DPDK patches and discussions
 help / color / mirror / Atom feed
From: <liljegren.mats2@gmail.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] pcap: Remove check for pcap_sendpacket
Date: Thu, 6 Mar 2014 10:00:40 +0100	[thread overview]
Message-ID: <1394096440-50930-2-git-send-email-liljegren.mats2@gmail.com> (raw)
In-Reply-To: <1394096440-50930-1-git-send-email-liljegren.mats2@gmail.com>

From: Mats Liljegren <mats.liljegren@enea.com>

Current test relies on the fact that pcap_sendpacket is a macro. Since it is
a function, the test fails, causing loss of sending ability when using pcap.

Signed-off-by: Mats Liljegren <mats.liljegren@enea.com>
---
 lib/librte_pmd_pcap/rte_eth_pcap.h |    4 ----
 1 file changed, 4 deletions(-)

diff --git a/lib/librte_pmd_pcap/rte_eth_pcap.h b/lib/librte_pmd_pcap/rte_eth_pcap.h
index c0bc5d8..0e28e0b 100644
--- a/lib/librte_pmd_pcap/rte_eth_pcap.h
+++ b/lib/librte_pmd_pcap/rte_eth_pcap.h
@@ -39,11 +39,7 @@ extern "C" {
 #endif
 #include <pcap.h>
 
-#ifdef pcap_sendpacket
 #define PCAP_CAN_SEND
-#else
-#undef PCAP_CAN_SEND
-#endif
 
 #define RTE_ETH_PCAP_PARAM_NAME "eth_pcap"
 
-- 
1.7.10.4

  reply	other threads:[~2014-03-06  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 19:13 [dpdk-dev] Pcap question Meir Tseitlin
2014-03-02 20:11 ` Olivier MATZ
2014-03-03 19:31   ` Meir Tseitlin
2014-03-03 20:32     ` Olivier MATZ
2014-03-03 21:09       ` Meir Tseitlin
2014-03-03 21:31         ` Olivier MATZ
2014-03-03 21:37           ` Olivier MATZ
2014-03-03 21:45             ` Meir Tseitlin
2014-03-05 20:32               ` Meir Tseitlin
2014-03-06  9:00                 ` liljegren.mats2
2014-03-06  9:00                   ` liljegren.mats2 [this message]
2014-03-06 10:10                   ` David Marchand
2014-03-20 16:38               ` Thomas Monjalon

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=1394096440-50930-2-git-send-email-liljegren.mats2@gmail.com \
    --to=liljegren.mats2@gmail.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).