patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "gage.eads@intel.com" <gage.eads@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Subject: Re: [dpdk-stable] [PATCH] eventdev: fix xstats documentation typo
Date: Sun, 16 Dec 2018 17:31:36 +0000	[thread overview]
Message-ID: <6c44501bfef633a761db765674b307b1f0ddfa51.camel@marvell.com> (raw)
In-Reply-To: <20181203200504.3176-1-gage.eads@intel.com>

On Mon, 2018-12-03 at 14:05 -0600, Gage Eads wrote:
> The eventdev extended stats documentation referred to two non-
> existent
> functions, rte_eventdev_xstats_get and
> rte_eventdev_get_xstats_by_name.
> 
> Fixes: 3ed7fc039a ("eventdev: add extended stats")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Gage Eads <gage.eads@intel.com>
> 

Applied to dpdk-next-eventdev/master. Thanks.



      reply	other threads:[~2018-12-16 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 20:05 Gage Eads
2018-12-16 17:31 ` Jerin Jacob Kollanukkaran [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=6c44501bfef633a761db765674b307b1f0ddfa51.camel@marvell.com \
    --to=jerinj@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@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).