From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 721] Wrong event pointer in rx adapter
Date: Mon, 21 Jun 2021 09:20:01 +0000 [thread overview]
Message-ID: <bug-721-3-3ng1v7omdQ@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-721-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=721
Pavan Nikhilesh Bhagavatula (pbhagavatula@marvell.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
CC| |pbhagavatula@marvell.com
--- Comment #7 from Pavan Nikhilesh Bhagavatula (pbhagavatula@marvell.com) ---
As Jay mentioned, the intent is to give the callback events generated in the
current Rx cycle which the current code already does.
Marking the bug as resolved.
Pavan.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-06-21 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 8:23 bugzilla
2021-05-26 9:54 ` Van Haaren, Harry
2021-05-26 13:02 ` Pavan Nikhilesh Bhagavatula
2021-05-27 8:18 ` Van Haaren, Harry
2021-06-01 6:23 ` Jayatheerthan, Jay
2021-06-21 9:20 ` 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-721-3-3ng1v7omdQ@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).