From: lijuan.tu@intel.com
To: dts@dpdk.org,qi.fu@intel.com,hailinx xu <hailinx.xu@intel.com>
Cc: hailinx xu <hailinx.xu@intel.com>
Subject: [dts][PATCH v3 1/2] test_plans: support ipv6 next proto id
Date: 27 Sep 2022 22:46:54 -0700 [thread overview]
Message-ID: <e7de8f$sagtji@fmsmga005-auth.fm.intel.com> (raw)
In-Reply-To: <20220922052839.23851-2-hailinx.xu@intel.com>
On Thu, 22 Sep 2022 13:28:38 +0800, hailinx xu <hailinx.xu@intel.com> wrote:
> add new test cases for ice support ipv6 next protocol id
>
> Signed-off-by: hailinx xu <hailinx.xu@intel.com>
Acked-by: Lijuan Tu <lijuan.tu@intel.com>
Series applied, thanks
next prev parent reply other threads:[~2022-09-28 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 5:28 [dts][PATCH v3 0/2] add new test plans and test cases hailinx xu
2022-09-22 5:28 ` [dts][PATCH v3 1/2] test_plans: support ipv6 next proto id hailinx xu
2022-09-28 5:46 ` lijuan.tu [this message]
2022-09-22 5:28 ` [dts][PATCH v3 2/2] tests/ice_fdir: " hailinx xu
2022-09-22 8:50 ` Huang, ZhiminX
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='e7de8f$sagtji@fmsmga005-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=hailinx.xu@intel.com \
--cc=qi.fu@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).