DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>,
	"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: "narender.vangati@intel.com" <narender.vangati@intel.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [v6 1/2] cryptodev: support enqueue & dequeue callback functions
Date: Fri, 30 Oct 2020 18:28:49 +0000	[thread overview]
Message-ID: <VI1PR04MB31683AD536BA31C84FEAF42FE6150@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1603926611-19086-2-git-send-email-abhinandan.gujjar@intel.com>

Hi Abhinandan,

> +struct rte_cryptodev_cb {
> +	struct rte_cryptodev_cb *next;
> +	/** < Pointer to next callback */
> +	rte_cryptodev_callback_fn fn;
> +	/** < Pointer to callback function */
> +	void *arg;
> +	/** < Pointer to argument */
> +};
> +
> +/**
> + * @internal
> + * Structure used to hold information about the RCU for a queue pair.
> + */
> +struct rte_cryptodev_cb_rcu {
> +	struct rte_cryptodev_cb *next;
> +	/** < Pointer to next callback */
> +	struct rte_rcu_qsbr *qsbr;
> +	/** < RCU QSBR variable per queue pair */
> +};
> +#endif
There is an extra space in each of the comments above between * and <.
Check other doxygen errors if any.

I believe the timestamp in your system is not correct, as the patchwork show
Date of 2 days back while the patches are sent today.
Could you please check? I believe CI server is not picking your patches for auto build.
Please correct it so that auto build can happen. None of your version was picked by CI.

  reply	other threads:[~2020-10-30 18:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 23:10 [dpdk-dev] [v6 0/2] support enqueue & dequeue callbacks on cryptodev Abhinandan Gujjar
2020-10-28 23:10 ` [dpdk-dev] [v6 1/2] cryptodev: support enqueue & dequeue callback functions Abhinandan Gujjar
2020-10-30 18:28   ` Akhil Goyal [this message]
2020-10-30 18:36     ` Gujjar, Abhinandan S
2020-11-02  9:37       ` Gujjar, Abhinandan S
2020-11-02 18:57         ` Akhil Goyal
2020-11-03  5:50           ` Gujjar, Abhinandan S
2020-11-03  6:28             ` Akhil Goyal
2020-11-03  7:44               ` Gujjar, Abhinandan S
2020-11-03 16:04                 ` Thomas Monjalon
2020-11-03 16:37                   ` Gujjar, Abhinandan S
2020-11-03 16:53                     ` Akhil Goyal
2020-11-03 17:03                       ` Gujjar, Abhinandan S
2020-11-03 17:07                         ` Akhil Goyal
2020-10-28 23:10 ` [dpdk-dev] [v6 2/2] test: add testcase for crypto enqueue callback Abhinandan Gujjar

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=VI1PR04MB31683AD536BA31C84FEAF42FE6150@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=narender.vangati@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).