From: Nipun Gupta <nipun.gupta@nxp.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"gage.eads@intel.com" <gage.eads@intel.com>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eventdev: amend timeout criteria comment for burst dequeue
Date: Wed, 8 Mar 2017 07:29:03 +0000 [thread overview]
Message-ID: <DB6PR0401MB2520AC1D54AC2E0421AA7AA9E62E0@DB6PR0401MB2520.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20170306132203.GA7006@localhost.localdomain>
Thanks Jerin. Patchwork still shows this patch in new state.
Does this matter or shall I move it to accepted state?
Regards,
Nipun
> -----Original Message-----
> From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> Sent: Monday, March 06, 2017 18:52
> To: Nipun Gupta <nipun.gupta@nxp.com>
> Cc: dev@dpdk.org; Hemant Agrawal <hemant.agrawal@nxp.com>;
> bruce.richardson@intel.com; gage.eads@intel.com;
> harry.van.haaren@intel.com
> Subject: Re: [PATCH v3] eventdev: amend timeout criteria comment for burst
> dequeue
>
> On Fri, Feb 10, 2017 at 09:56:50PM +0530, Nipun Gupta wrote:
> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> > Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> Applied to dpdk-next-eventdev/master. Thanks.
>
> > ---
> > Changes for v2:
> > - Fix errors reported by check-git-log.sh
> > Changes for v3:
> > - Corrected comment's language
> >
> > lib/librte_eventdev/rte_eventdev.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/librte_eventdev/rte_eventdev.h
> b/lib/librte_eventdev/rte_eventdev.h
> > index c2f9310..29f0f46 100644
> > --- a/lib/librte_eventdev/rte_eventdev.h
> > +++ b/lib/librte_eventdev/rte_eventdev.h
> > @@ -1216,7 +1216,7 @@ struct rte_eventdev {
> > * - 0 no-wait, returns immediately if there is no event.
> > * - >0 wait for the event, if the device is configured with
> > * RTE_EVENT_DEV_CFG_PER_DEQUEUE_TIMEOUT then this function will
> wait until
> > - * the event available or *timeout_ticks* time.
> > + * at least one event is available or *timeout_ticks* time.
> > * if the device is not configured with
> RTE_EVENT_DEV_CFG_PER_DEQUEUE_TIMEOUT
> > * then this function will wait until the event available or
> > * *dequeue_timeout_ns* ns which was previously supplied to
> > --
> > 1.9.1
> >
next prev parent reply other threads:[~2017-03-08 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:04 [dpdk-dev] [PATCH] eventdev: amend comment for timeout_ticks in rte_event_dequeue_burst() Nipun Gupta
2017-02-10 15:47 ` [dpdk-dev] [PATCH v2] eventdev: amend timeout criteria comment for burst dequeue Nipun Gupta
2017-02-10 10:00 ` Van Haaren, Harry
2017-02-10 16:26 ` [dpdk-dev] [PATCH v3] " Nipun Gupta
2017-03-06 13:22 ` Jerin Jacob
2017-03-08 7:29 ` Nipun Gupta [this message]
2017-03-08 12:49 ` Jerin Jacob
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=DB6PR0401MB2520AC1D54AC2E0421AA7AA9E62E0@DB6PR0401MB2520.eurprd04.prod.outlook.com \
--to=nipun.gupta@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).