From: Thomas Monjalon <thomas@monjalon.net>
To: Matan Azrad <matan@mellanox.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: allow all ports event registration
Date: Fri, 29 Dec 2017 12:45:12 +0100 [thread overview]
Message-ID: <6214136.ixGVTiWP3P@xps> (raw)
In-Reply-To: <1512402221-17630-1-git-send-email-matan@mellanox.com>
Hi Matan,
Please find some review details below.
As this patch is needed for the notification of new ports,
I will re-send them in a patchset, with the minor modifications
described below.
04/12/2017 16:43, Matan Azrad:
> --- a/lib/librte_ether/rte_ethdev.c
> +++ b/lib/librte_ether/rte_ethdev.c
> +RTE_INIT(eth_dev_init_cb_lists);
[...]
> +static void
> +eth_dev_init_cb_lists(void)
RTE_INIT macro can be used in function definition
without prior declaration.
This function should be moved just before the callback
register/unregister functions.
> @@ -2827,37 +2837,59 @@
> + uint32_t next_port;
> + uint32_t last_port;
A port id should be uint16_t.
> --- a/lib/librte_ether/rte_ethdev.h
> +++ b/lib/librte_ether/rte_ethdev.h
> /**
> - * Register a callback function for specific port id.
> + * Register a callback function for port id event.
[...]
> - * Unregister a callback function for specific port id.
> + * Unregister a callback function for port id event.
"port event" would be more appropriate than "port id event".
next prev parent reply other threads:[~2017-12-29 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 7:49 [dpdk-dev] [PATCH] " Matan Azrad
2017-12-04 15:43 ` [dpdk-dev] [PATCH v2] " Matan Azrad
2017-12-29 11:45 ` Thomas Monjalon [this message]
2017-12-30 19:04 ` Matan Azrad
2017-12-30 20:51 ` Thomas Monjalon
2017-12-30 21:14 ` Matan Azrad
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=6214136.ixGVTiWP3P@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@mellanox.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).