From: "Chu, Haijun" <haijun.chu@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Han, YingyaX" <yingyax.han@intel.com>
Subject: RE: [dts][PATCH V1 3/3]conf: add ice_header_split_perf configuration file
Date: Tue, 27 Dec 2022 05:40:24 +0000 [thread overview]
Message-ID: <BYAPR11MB2663C7E603C554D230975BAE8EED9@BYAPR11MB2663.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221226065551.10065-1-yingyax.han@intel.com>
Acked-by: Haijun Chu<haijun.chu@intel.com>
-----Original Message-----
From: Yingya Han <yingyax.han@intel.com>
Sent: Monday, December 26, 2022 2:56 PM
To: dts@dpdk.org
Cc: Han, YingyaX <yingyax.han@intel.com>
Subject: [dts][PATCH V1 3/3]conf: add ice_header_split_perf configuration file
Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
next prev parent reply other threads:[~2022-12-27 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 6:55 Yingya Han
2022-12-27 5:40 ` Chu, Haijun [this message]
2023-01-04 0:58 ` lijuan.tu
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=BYAPR11MB2663C7E603C554D230975BAE8EED9@BYAPR11MB2663.namprd11.prod.outlook.com \
--to=haijun.chu@intel.com \
--cc=dts@dpdk.org \
--cc=yingyax.han@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).