From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Carrillo, Erik G" <erik.g.carrillo@intel.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: update references to removed function
Date: Tue, 30 Apr 2019 11:22:08 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F6085D7@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1556548686-32767-1-git-send-email-erik.g.carrillo@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Erik Gabriel Carrillo
> Sent: Monday, April 29, 2019 3:38 PM
> To: jerin.jacob@caviumnetworks.com
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v2] doc: update references to removed function
>
> Remove references to the (deleted) rte_event_port_enqueue_depth() function
> in the Doxygen comments for rte_event_enqueue_burst() and friends, and
> replace with references to rte_event_port_attr_get().
>
> Fixes: 78ffab961155 ("eventdev: add port attribute function")
> Fixes: c9bf83947e2e ("eventdev: add eth Tx adapter APIs")
> Cc: stable@dpdk.org
>
> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Please mark the previous version as superseded in patchwork.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2019-04-30 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 16:53 [dpdk-dev] [PATCH] " Erik Gabriel Carrillo
2019-04-26 16:53 ` Erik Gabriel Carrillo
2019-04-28 18:14 ` Jerin Jacob Kollanukkaran
2019-04-28 18:14 ` Jerin Jacob Kollanukkaran
2019-04-29 14:38 ` [dpdk-dev] [PATCH v2] " Erik Gabriel Carrillo
2019-04-29 14:38 ` Erik Gabriel Carrillo
2019-04-30 11:22 ` Mcnamara, John [this message]
2019-04-30 11:22 ` Mcnamara, John
2019-05-04 21:20 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-05-04 21:20 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE23F6085D7@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@dpdk.org \
/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).