From: Bruce Richardson <bruce.richardson@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: Gage Eads <gage.eads@intel.com>,
dev@dpdk.org, hemant.agrawal@nxp.com, harry.van.haaren@intel.com,
nipun.gupta@nxp.com
Subject: Re: [dpdk-dev] [PATCH v2] eventdev: clarify nb_links and nb_unlinks description
Date: Thu, 16 Feb 2017 10:34:54 +0000 [thread overview]
Message-ID: <20170216103454.GA99272@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20170214040512.GA6091@localhost.localdomain>
On Tue, Feb 14, 2017 at 09:35:13AM +0530, Jerin Jacob wrote:
> On Mon, Feb 13, 2017 at 09:52:53AM -0600, Gage Eads wrote:
> > This commit clarifies the usage of nb_links and nb_unlinks when passing
> > a NULL pointer as the queues argument.
> >
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
Applied to dpdk-next-eventdev
/Bruce
prev parent reply other threads:[~2017-02-16 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 19:04 [dpdk-dev] [PATCH] eventdev: clarify " Gage Eads
2017-02-11 6:29 ` Jerin Jacob
2017-02-13 15:52 ` [dpdk-dev] [PATCH v2] eventdev: clarify nb_links and " Gage Eads
2017-02-14 4:05 ` Jerin Jacob
2017-02-16 10:34 ` 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=20170216103454.GA99272@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).