From: John Miller <john.miller@atomicrules.com>
To: dev@dpdk.org
Cc: shepard.siegel@atomicrules.com, ed.czeck@atomicrules.com,
John Miller <john.miller@atomicrules.com>
Subject: [dpdk-dev] [PATCH v2 0/3] net/ark: augment user extension and bug fix
Date: Wed, 28 Jun 2017 06:08:21 -0400 [thread overview]
Message-ID: <1498644504-30252-1-git-send-email-john.miller@atomicrules.com> (raw)
In-Reply-To: <1498134644-14089-1-git-send-email-john.miller@atomicrules.com>
v2:
* Split the user extension private data per port patch and the
set_mtu patch into separate patches.
* Add better description to per port private data patch
* stats_reset patch untouched from V1
John Miller (3):
net/ark: allow unique user data for each port in extension calls
net/ark: add set_mtu call to user extension API
net/ark: fix bug in stats_reset operation
drivers/net/ark/ark_ethdev.c | 72 ++++++++++++++++++++++++++++++++------------
drivers/net/ark/ark_ext.h | 4 +++
drivers/net/ark/ark_global.h | 5 +--
3 files changed, 60 insertions(+), 21 deletions(-)
--
1.9.1
next prev parent reply other threads:[~2017-06-28 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 12:30 [dpdk-dev] [PATCH 1/2] net/ark: allow unique user data for each port in extension calls John Miller
2017-06-22 12:30 ` [dpdk-dev] [PATCH 2/2] net/ark: fix bug in stats_reset operation John Miller
2017-06-23 9:21 ` [dpdk-dev] [PATCH 1/2] net/ark: allow unique user data for each port in extension calls Ferruh Yigit
2017-06-23 10:06 ` Shepard Siegel
2017-06-28 10:08 ` John Miller [this message]
2017-06-28 10:08 ` [dpdk-dev] [PATCH v2 1/3] " John Miller
2017-06-28 10:08 ` [dpdk-dev] [PATCH v2 2/3] net/ark: add set_mtu call to user extension API John Miller
2017-06-28 10:08 ` [dpdk-dev] [PATCH v2 3/3] net/ark: fix bug in stats_reset operation John Miller
2017-06-28 12:39 ` [dpdk-dev] [PATCH v2 0/3] net/ark: augment user extension and bug fix Ferruh Yigit
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=1498644504-30252-1-git-send-email-john.miller@atomicrules.com \
--to=john.miller@atomicrules.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).