test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "xu,gang" <gangx.xu@intel.com>, dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: Re: [dts] [PATCH V2] fix link status interrupt failed case
Date: Sat, 09 Sep 2017 00:21:34 +0800	[thread overview]
Message-ID: <59B2C38E.6020501@intel.com> (raw)
In-Reply-To: <1504853194-8552-1-git-send-email-gangx.xu@intel.com>

Thanks, huilong. Applied.

On 09/08/2017 02:46 PM, xu,gang wrote:
> From: "xu,huilong"<huilongx.xu@intel.com>
>
>      update list:
>      1. update fortville nic test interrupt mode list
>      2. fix example setup failed
>      3. fix check port stats in example
>      4. fix check rx/tx packet get count number error
>
> Signed-off-by: xu,huilong<huilongx.xu@intel.com>

      reply	other threads:[~2017-09-08  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  6:46 xu,gang
2017-09-08 16:21 ` Liu, Yong [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=59B2C38E.6020501@intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=gangx.xu@intel.com \
    --cc=huilongx.xu@intel.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).