DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Jay Jayatheerthan <jay.jayatheerthan@intel.com>,
	dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eventdev: fix doxygen for function declaration
Date: Mon, 12 Apr 2021 12:57:03 +0530	[thread overview]
Message-ID: <CALBAE1NxjagEJsY3cbWJao+91RzcOn4GApQYTK5Y2Nzshhrz5w@mail.gmail.com> (raw)
In-Reply-To: <20210409132043.949-1-pbhagavatula@marvell.com>

On Fri, Apr 9, 2021 at 6:50 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix missing parameters in doxygen of function declaration.
>
> Fixes: 5b1337f0a08a ("eventdev: introduce event vector Rx capability")

Squashed to this change in the next-eventdev tree.

>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>


> ---
>  lib/librte_eventdev/rte_event_eth_rx_adapter.h | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/lib/librte_eventdev/rte_event_eth_rx_adapter.h b/lib/librte_eventdev/rte_event_eth_rx_adapter.h
> index 7407cde00..182dd2e5d 100644
> --- a/lib/librte_eventdev/rte_event_eth_rx_adapter.h
> +++ b/lib/librte_eventdev/rte_event_eth_rx_adapter.h
> @@ -563,6 +563,9 @@ int rte_event_eth_rx_adapter_vector_limits_get(
>   *  If rx_queue_id is -1, then all Rx queues configured for the ethernet device
>   *  are configured with event vectorization.
>   *
> + * @param config
> + *  Event vector configuration structure.
> + *
>   * @return
>   *  - 0: Success, Receive queue configured correctly.
>   *  - <0: Error code on failure.
> --
> 2.17.1
>

      reply	other threads:[~2021-04-12  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 13:20 pbhagavatula
2021-04-12  7:27 ` Jerin Jacob [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=CALBAE1NxjagEJsY3cbWJao+91RzcOn4GApQYTK5Y2Nzshhrz5w@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jay.jayatheerthan@intel.com \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.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).