DPDK patches and discussions
 help / color / mirror / Atom feed
From: Scott Daniels <daniels@research.att.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com, wenzhuo.lu@intel.com,
	larry <liang-min.wang@intel.com>, alex zelezniak <az5157@att.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add the description for option pflink_fullchk in ixgbevf
Date: Fri, 7 Jun 2019 07:31:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LSU.2.20.12.1906070729270.12860@localhost> (raw)
In-Reply-To: <1559877042-95011-4-git-send-email-haiyue.wang@intel.com>


Acked-by: Scott Daniels daniels@research.att.com

On Thu, 6 Jun 2019, Haiyue Wang wrote:

> Add the detail description for this pflink_fullchk option, when it will
> be used, and it is used for fixing what kind of issue.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>

  reply	other threads:[~2019-06-07 11:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  3:10 [dpdk-dev] [PATCH v1 1/2] net/ixgbevf: add an option pflink_fullchk to get link status quickly Haiyue Wang
2019-06-07  3:10 ` [dpdk-dev] [PATCH v1 2/2] doc: add the description for option pflink_fullchk in ixgbevf Haiyue Wang
2019-06-07  3:10 ` [dpdk-dev] [PATCH 1/2] net/ixgbevf: add an option pflink_fullchk to get link status quickly Haiyue Wang
2019-06-07  3:10 ` [dpdk-dev] [PATCH 2/2] doc: add the description for option pflink_fullchk in ixgbevf Haiyue Wang
2019-06-07 11:31   ` Scott Daniels [this message]
2019-06-07 12:25   ` Kevin Traynor
2019-06-07 13:55     ` Wang, Haiyue
2019-06-07 14:38       ` Kevin Traynor
2019-06-07 15:10         ` Wang, Haiyue

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=alpine.LSU.2.20.12.1906070729270.12860@localhost \
    --to=daniels@research.att.com \
    --cc=az5157@att.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=liang-min.wang@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).