From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1349] Traffic filtering when capturing packets
Date: Thu, 15 Feb 2024 14:55:40 +0000 [thread overview]
Message-ID: <bug-1349-3-Vfl3YM5fw4@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1349-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1349
Patrick Robb (probb@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Patrick Robb (probb@iol.unh.edu) ---
We will verify testsuite success based solely on considering the
characteristics of the packets sent, then compare against the list of packets
received at the end. No packet filtering system will be integrated into the
framework.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2690 bytes --]
prev parent reply other threads:[~2024-02-15 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 9:24 [Bug " bugzilla
2024-02-15 14:55 ` bugzilla [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=bug-1349-3-Vfl3YM5fw4@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).