From: Bruce Richardson <bruce.richardson@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Nipun Gupta <nipun.gupta@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"Eads, Gage" <gage.eads@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eventdev: amend comments for events limit and threshold
Date: Wed, 15 Feb 2017 14:56:53 +0000 [thread overview]
Message-ID: <20170215145652.GB85444@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA6129F22C9@IRSMSX102.ger.corp.intel.com>
On Wed, Feb 15, 2017 at 01:53:45PM +0000, Van Haaren, Harry wrote:
> > From: Nipun Gupta [mailto:nipun.gupta@nxp.com]
> > Sent: Tuesday, February 14, 2017 12:43 PM
> > To: dev@dpdk.org
> > Cc: hemant.agrawal@nxp.com; jerin.jacob@caviumnetworks.com; Richardson, Bruce
> > <bruce.richardson@intel.com>; Eads, Gage <gage.eads@intel.com>; Van Haaren, Harry
> > <harry.van.haaren@intel.com>; Nipun Gupta <nipun.gupta@nxp.com>
> > Subject: [PATCH v3] eventdev: amend comments for events limit and threshold
> >
> > Updated the comments on 'nb_events_limit' of 'struct rte_event_dev_config'
> > and 'new_event_threshold' of 'struct rte_event_port_conf'.
> >
> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
>
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
Applied to dpdk-next-eventdev
/Bruce
prev parent reply other threads:[~2017-02-15 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:05 [dpdk-dev] [PATCH] eventdev: amend comments for nb_events_limit and new_event_threshold Nipun Gupta
2017-02-10 15:50 ` [dpdk-dev] [PATCH v2] eventdev: amend comments for events limit and threshold Nipun Gupta
2017-02-10 10:31 ` Van Haaren, Harry
2017-02-11 9:48 ` Nipun Gupta
2017-02-13 7:53 ` Jerin Jacob
2017-02-14 12:42 ` [dpdk-dev] [PATCH v3] " Nipun Gupta
2017-02-15 13:53 ` Van Haaren, Harry
2017-02-15 14:56 ` Bruce Richardson [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=20170215145652.GB85444@bricha3-MOBL3.ger.corp.intel.com \
--to=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 \
--cc=nipun.gupta@nxp.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).