All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 2/5] pipeline: added bulk add/delete functions for table
Date: Thu, 08 Oct 2015 13:41:57 +0200	[thread overview]
Message-ID: <37034077.SclJjAr06D@xps13> (raw)
In-Reply-To: <1441967499-21255-3-git-send-email-maciejx.t.gajdzica@intel.com>

2015-09-11 12:31, Maciej Gajdzica:
> +/**
> + * Pipeline table entry delete bulk
> + *
> + * @param p
> + *   Handle to pipeline instance
> + * @param table_id
> + *   Table ID (returned by previous invocation of pipeline table create)
> + * @param keys
> + *   Array containing table entry keys
> + * @param key_found
> + *   On successful invocation, key_found for every item in the array is set to
> + *   TRUE (value different than 0) if key was found in the table before the
> + *   delete operation and to FALSE (value 0) if not
> + * @param entries
> + *   If entries pointer is NULL, this pointer is ignored for every entry found.
> + *   Else, after successful invocation, if specific key is found in the table
> + *   and entry points to a valid buffer, the table entry contents (as it was
> + *   before the delete was performed) is copied to this buffer.
> + * @return
> + *   0 on success, error code otherwise
> + */
> +int rte_pipeline_table_entry_delete_bulk(struct rte_pipeline *p,
> +	uint32_t table_id,
> +	void **keys,
> +	uint32_t n_keys,
> +	int *key_found,
> +	struct rte_pipeline_table_entry **entries);

The parameter n_keys is not documented.
Doxygen is reporting the error.

  reply	other threads:[~2015-10-08 11:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 10:31 [PATCH v2 0/5] pipeline: add bulk add/delete functions for table Maciej Gajdzica
2015-09-11 10:31 ` [PATCH v2 1/5] table: added " Maciej Gajdzica
2015-09-11 10:31 ` [PATCH v2 2/5] pipeline: " Maciej Gajdzica
2015-10-08 11:41   ` Thomas Monjalon [this message]
2015-10-12  8:10     ` Azarewicz, PiotrX T
2015-09-11 10:31 ` [PATCH v2 3/5] test_table: added check for bulk add/delete to acl table unit test Maciej Gajdzica
2015-09-11 10:31 ` [PATCH v2 4/5] ip_pipeline: added cli commands for bulk add/delete to firewall pipeline Maciej Gajdzica
2015-09-11 10:31 ` [PATCH v2 5/5] doc: modify release notes and deprecation notice for table and pipeline Maciej Gajdzica
2015-10-08 11:42   ` Thomas Monjalon
2015-10-12  7:53     ` Azarewicz, PiotrX T
2015-10-12  8:22       ` Thomas Monjalon
2015-10-12  8:27         ` Azarewicz, PiotrX T
2015-09-11 11:11 ` [PATCH v2 0/5] pipeline: add bulk add/delete functions for table Dumitrescu, Cristian
2015-10-13  7:34 ` [PATCH v3 " Marcin Kerlin
2015-10-13  7:34   ` [PATCH v3 1/5] table: added " Marcin Kerlin
2015-10-13  7:34   ` [PATCH v3 2/5] pipeline: " Marcin Kerlin
2015-10-13  7:34   ` [PATCH v3 3/5] test_table: added check for bulk add/delete to acl table unit test Marcin Kerlin
2015-10-19 15:30     ` Thomas Monjalon
2015-10-13  7:34   ` [PATCH v3 4/5] ip_pipline: added cli commands for bulk add/delete to firewall pipeline Marcin Kerlin
2015-10-13  7:34   ` [PATCH v3 5/5] doc: modify release notes and deprecation notice for table and pipeline Marcin Kerlin

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=37034077.SclJjAr06D@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=maciejx.t.gajdzica@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.