DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 0/2] net/netvsc: xstat fixes
Date: Thu, 27 Jun 2019 19:33:11 +0100	[thread overview]
Message-ID: <db1a4f0d-4306-e0e6-0da8-7ec70964211b@intel.com> (raw)
In-Reply-To: <20190620220924.32079-1-stephen@networkplumber.org>

On 6/20/2019 11:09 PM, Stephen Hemminger wrote:
> A couple of fixes for the xstats functionality in netvsc PMD.
> 
> Mohsin Mazhar Shaikh (1):
>   net/netvsc: set id in xstats_get
> 
> Stephen Hemminger (1):
>   net/netvsc: fix xstats for VF device

Series applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2019-06-27 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 22:09 [dpdk-dev] " Stephen Hemminger
2019-06-20 22:09 ` [dpdk-dev] [PATCH 1/2] net/netvsc: set id in xstats_get Stephen Hemminger
2019-06-20 22:09 ` [dpdk-dev] [PATCH 2/2] net/netvsc: fix xstats for VF device Stephen Hemminger
2019-06-27 18:33 ` Ferruh Yigit [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=db1a4f0d-4306-e0e6-0da8-7ec70964211b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).