From: lijuan.tu@intel.com
To: dts@dpdk.org,Lingli Chen <linglix.chen@intel.com>
Cc: zhiminx.huang@intel.com,Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V2 3/3] tests/*: add NIC IGC-I226_LM in support suites
Date: 28 Jun 2022 18:34:23 -0700 [thread overview]
Message-ID: <cc41e7$jjrfd5@fmsmga004-auth.fm.intel.com> (raw)
In-Reply-To: <20220624063555.5442-3-linglix.chen@intel.com>
On Fri, 24 Jun 2022 02:35:55 -0400, Lingli Chen <linglix.chen@intel.com> wrote:
> add NIC IGC-I226_LM in 12 support suites
>
> Signed-off-by: Lingli Chen <linglix.chen@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-06-29 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 6:35 [dts][PATCH V2 1/3] framework: add NIC IGC-I226_LM identifiers Lingli Chen
2022-06-24 6:35 ` [dts][PATCH V2 2/3] conf/test_case_*: add NIC IGC-I226_LM in support cases Lingli Chen
2022-06-24 6:35 ` [dts][PATCH V2 3/3] tests/*: add NIC IGC-I226_LM in support suites Lingli Chen
2022-06-29 1:34 ` lijuan.tu [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='cc41e7$jjrfd5@fmsmga004-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=linglix.chen@intel.com \
--cc=zhiminx.huang@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).