From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, thomas@monjalon.net
Cc: "Bernard.Iremonger" <Bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH v2 3/4] examples: callback process API changes
Date: Mon, 12 Jun 2017 16:18:10 +0100 [thread overview]
Message-ID: <1497280691-18641-4-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1495191794-9112-1-git-send-email-bernard.iremonger@intel.com>
From: "Bernard.Iremonger" <Bernard.iremonger@intel.com>
Modify the link_status_interrupt sample application for
the rte_eth_dev_callback_process API changes.
Signed-off-by: Bernard.Iremonger <Bernard.iremonger@intel.com>
---
examples/link_status_interrupt/main.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/examples/link_status_interrupt/main.c b/examples/link_status_interrupt/main.c
index 25da28e..d585789 100644
--- a/examples/link_status_interrupt/main.c
+++ b/examples/link_status_interrupt/main.c
@@ -469,14 +469,16 @@ struct lsi_port_statistics {
* Pointer to(address of) the parameters.
*
* @return
- * void.
+ * int.
*/
-static void
-lsi_event_callback(uint8_t port_id, enum rte_eth_event_type type, void *param)
+static int
+lsi_event_callback(uint8_t port_id, enum rte_eth_event_type type, void *param,
+ void *ret_param)
{
struct rte_eth_link link;
RTE_SET_USED(param);
+ RTE_SET_USED(ret_param);
printf("\n\nIn registered callback...\n");
printf("Event type: %s\n", type == RTE_ETH_EVENT_INTR_LSC ? "LSC interrupt" : "unknown event");
@@ -488,6 +490,8 @@ struct lsi_port_statistics {
("full-duplex") : ("half-duplex"));
} else
printf("Port %d Link Down\n\n", port_id);
+
+ return 0;
}
/* Check the link status of all ports in up to 9s, and print them finally */
--
1.9.1
next prev parent reply other threads:[~2017-06-12 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 11:03 [dpdk-dev] [PATCH v1 0/4] ethdev: callback process API Bernard Iremonger
2017-05-19 11:03 ` [dpdk-dev] [PATCH v1 1/4] ethdev: modify " Bernard Iremonger
2017-05-19 11:03 ` [dpdk-dev] [PATCH v1 2/4] test: callback process API changes Bernard Iremonger
2017-05-19 11:03 ` [dpdk-dev] [PATCH v1 3/4] examples: " Bernard Iremonger
2017-05-19 11:03 ` [dpdk-dev] [PATCH v1 4/4] doc: remove deprecation notice Bernard Iremonger
2017-06-12 15:18 ` [dpdk-dev] [PATCH v2 0/4] ethdev: callback process API Bernard Iremonger
2017-06-15 12:29 ` [dpdk-dev] [PATCH v3] " Bernard Iremonger
2017-06-15 12:29 ` [dpdk-dev] [PATCH v3] ethdev: modify " Bernard Iremonger
2017-07-01 15:19 ` Thomas Monjalon
2017-07-03 9:01 ` Ferruh Yigit
2017-07-03 9:04 ` Ferruh Yigit
2017-07-03 11:06 ` Iremonger, Bernard
2017-07-03 11:18 ` Ferruh Yigit
2017-07-03 11:28 ` Iremonger, Bernard
2017-07-03 11:40 ` Thomas Monjalon
2017-06-12 15:18 ` [dpdk-dev] [PATCH v2 1/4] " Bernard Iremonger
2017-06-14 21:22 ` Thomas Monjalon
2017-06-15 10:56 ` Iremonger, Bernard
2017-06-15 15:43 ` Stephen Hemminger
2017-06-21 9:22 ` Iremonger, Bernard
2017-06-12 15:18 ` [dpdk-dev] [PATCH v2 2/4] test: callback process API changes Bernard Iremonger
2017-06-12 15:18 ` Bernard Iremonger [this message]
2017-06-12 15:18 ` [dpdk-dev] [PATCH v2 4/4] doc: remove deprecation notice Bernard Iremonger
2017-06-13 8:52 ` Mcnamara, John
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=1497280691-18641-4-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).