From: lijuan.tu@intel.com
To: dts@dpdk.org,Song Jiale <songx.jiale@intel.com>
Cc: Song Jiale <songx.jiale@intel.com>
Subject: [dts] [PATCH V3 2/2] tests/ice_dcf_data_path: rename suite
Date: 18 Sep 2022 18:25:37 -0700 [thread overview]
Message-ID: <b72376$gv2gbk@orsmga003-auth.jf.intel.com> (raw)
In-Reply-To: <20220908111148.8023-2-songx.jiale@intel.com>
On Thu, 8 Sep 2022 11:11:48 +0000, Song Jiale <songx.jiale@intel.com> wrote:
> 1. rename the name of ice_dcf_date_path to ice_dcf_data_path.
> 2. synchronize testplan modifications.
>
> Signed-off-by: Song Jiale <songx.jiale@intel.com>
Acked-by: Lijuan Tu <lijuan.tu@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-09-19 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 11:11 [dts] [PATCH V3 1/2] test_plans/ice_dcf_data_path: " Song Jiale
2022-09-08 3:00 ` Jiale, SongX
2022-09-08 11:11 ` [dts] [PATCH V3 2/2] tests/ice_dcf_data_path: " Song Jiale
2022-09-08 2:59 ` Jiale, SongX
2022-09-08 6:27 ` Chen, LingliX
2022-09-19 1:25 ` 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='b72376$gv2gbk@orsmga003-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=songx.jiale@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).