test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>,
	"Xu, HailinX" <hailinx.xu@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH v4] test_plans:add iavf_flexible_descriptor
Date: Thu, 4 Mar 2021 08:43:51 +0000	[thread overview]
Message-ID: <fb8c348e9cce4c54965ac4c343f79826@intel.com> (raw)
In-Reply-To: <BN7PR11MB2658E25657DB680F2583976494979@BN7PR11MB2658.namprd11.prod.outlook.com>

> > v1: add test plan: iavf_flexible_descriptor.
> > v2: add test plan and Unified code style.
> > v3: modify hierarc.
> > v4: Fix trailing whitespace issues.
> >
> > Signed-off-by: Hailin Xu <hailinx.xu@intel.com>
> Acked-by: Lin Xueqin <Xueqin.lin@intel.com>

Applied

      reply	other threads:[~2021-03-04  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  7:04 Hailin Xu
2021-03-04  5:27 ` Lin, Xueqin
2021-03-04  8:43   ` Tu, Lijuan [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=fb8c348e9cce4c54965ac4c343f79826@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=hailinx.xu@intel.com \
    --cc=xueqin.lin@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).