From: lijuan.tu@intel.com
To: dts@dpdk.org,Jin Ling <jin.ling@intel.com>
Cc: yuan.peng@intel.com,lijuan.tu@intel.com,Jin Ling <jin.ling@intel.com>
Subject: [DTS][PATCH V2 1/1] tests/uni_pkt: optimize code for check result
Date: 27 Mar 2023 17:53:51 -0700 [thread overview]
Message-ID: <e21edb$oktpcg@fmsmga001-auth.fm.intel.com> (raw)
In-Reply-To: <20230309012341.752557-2-jin.ling@intel.com>
On Thu, 9 Mar 2023 09:23:41 +0800, Jin Ling <jin.ling@intel.com> wrote:
> The script only checks if there are flags in the output, but both hw and sw parts have flags,
> which may lead to incorrect test results, so modified the code in this part to check the hw flag only.
>
> Signed-off-by: Jin Ling <jin.ling@intel.com>
Applied, thanks
prev parent reply other threads:[~2023-03-28 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 1:23 [DTS][PATCH V2 0/1] uni_pkt:optimize script Jin Ling
2023-03-09 1:23 ` [DTS][PATCH V2 1/1] tests/uni_pkt: optimize code for check result Jin Ling
2023-03-28 0:53 ` 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='e21edb$oktpcg@fmsmga001-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=jin.ling@intel.com \
--cc=yuan.peng@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).