From: lijuan.tu@intel.com
To: dts@dpdk.org,Jun Dong <junx.dong@intel.com>
Cc: lijuan.tu@intel.com,qingx.sun@intel.com,junx.dong@intel.com
Subject: [dts] [6/6] tests/*: replace codename in test suites
Date: 11 May 2022 22:05:54 -0700 [thread overview]
Message-ID: <87f1b2$gs8f2b@orsmga007-auth.jf.intel.com> (raw)
In-Reply-To: <20220510095431.3270-7-junx.dong@intel.com>
On Tue, 10 May 2022 17:54:31 +0800, Jun Dong <junx.dong@intel.com> wrote:
> Signed-off-by: Jun Dong <junx.dong@intel.com>
Reviewed-by: Lijuan Tu <lijuan.tu@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-05-12 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:54 [dts] [0/6] modify about codename replacement Jun Dong
2022-05-10 9:54 ` [dts] [1/6] conf/*: replace codename in configuration in conf directory Jun Dong
2022-05-10 9:54 ` [dts] [2/6] doc/*: replace codename in doc Jun Dong
2022-05-10 9:54 ` [dts] [3/6] executions/*: replace codename in executeion configurations Jun Dong
2022-05-10 9:54 ` [dts] [4/6] framework/*: replace codename in framework Jun Dong
2022-05-10 9:54 ` [dts] [5/6] test_plans/*: replace codename in test plans Jun Dong
2022-05-10 9:54 ` [dts] [6/6] tests/*: replace codename in test suites Jun Dong
2022-05-12 5:05 ` 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='87f1b2$gs8f2b@orsmga007-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=junx.dong@intel.com \
--cc=qingx.sun@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).