DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] lpm: added a new rte_lpm_config structure for ipv4
Date: Wed, 09 Mar 2016 14:16:19 +0100	[thread overview]
Message-ID: <2251317.WsmSxiIWhQ@xps13> (raw)
In-Reply-To: <1457527410-8428-1-git-send-email-michalx.k.jastrzebski@intel.com>

2016-03-09 13:43, Michal Jastrzebski:
> From: Michal Kobylinski <michalx.kobylinski@intel.com>
>  struct rte_lpm *
> -rte_lpm_create(const char *name, int socket_id, int max_rules, int flags);
> +rte_lpm_create(const char *name, int socket_id,
> +		const struct rte_lpm_config *config);

The doxygen comment must be updated:
rte_lpm.h:215: warning: argument 'max_rules' of command @param is not found
in the argument list
rte_lpm.h:215: warning: argument 'flags' of command @param is not found
in the argument list
rte_lpm.h:236: warning: The following parameters are not documented:
  parameter 'config'

      reply	other threads:[~2016-03-09 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 20:57 [dpdk-dev] [PATCH 0/2] Added a new rte_lpm_config structure for IPv4 Michal Kobylinski
2016-03-08 20:57 ` [dpdk-dev] [PATCH 1/2] lpm: added a new rte_lpm_config structure for ipv4 Michal Kobylinski
2016-03-08 20:57 ` [dpdk-dev] [PATCH 2/2] examples: update to use new rte_lpm_config " Michal Kobylinski
2016-03-09  0:47 ` [dpdk-dev] [PATCH 0/2] Added a new rte_lpm_config structure for IPv4 Thomas Monjalon
2016-03-09 12:43 ` [dpdk-dev] [PATCH v2] lpm: added a new rte_lpm_config structure for ipv4 Michal Jastrzebski
2016-03-09 13:16   ` Thomas Monjalon [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=2251317.WsmSxiIWhQ@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=michalx.k.jastrzebski@intel.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).