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 V2] tests/rte_flow_common: optimize scripts
Date: 18 Nov 2022 00:50:51 -0800 [thread overview]
Message-ID: <d60617$isv7k1@orsmga007-auth.jf.intel.com> (raw)
In-Reply-To: <20221111113846.26996-1-songx.jiale@intel.com>
On Fri, 11 Nov 2022 11:38:46 +0000, Song Jiale <songx.jiale@intel.com> wrote:
> 1. some packages that mismatch the rule do not have hash values.
> add a parameter "check_hash_num" to determine whether to detect the number of hash values.
> 2. change "log_msg" to a string.
>
> Signed-off-by: Song Jiale <songx.jiale@intel.com>
Applied, thanks
prev parent reply other threads:[~2022-11-18 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 11:38 Song Jiale
2022-11-18 2:23 ` Li, WeiyuanX
2022-11-18 8:50 ` 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='d60617$isv7k1@orsmga007-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).