From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Wang, YuanX" <yuanx.wang@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"Zhang, Yuying" <yuying.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Ding, Xuan" <xuan.ding@intel.com>,
"Tang, Yaqi" <yaqi.tang@intel.com>
Subject: Re: [PATCH] app/testpmd: remove useless check
Date: Mon, 17 Oct 2022 11:36:42 +0300 [thread overview]
Message-ID: <e07835f6-2370-60d9-bcfe-714326537673@oktetlabs.ru> (raw)
In-Reply-To: <PH7PR11MB6953CCF5F968BB247742BDD785249@PH7PR11MB6953.namprd11.prod.outlook.com>
On 10/14/22 12:52, Wang, YuanX wrote:
> Hi Singh,
>
>> -----Original Message-----
>> From: Singh, Aman Deep <aman.deep.singh@intel.com>
>> Sent: Friday, October 14, 2022 5:37 PM
>> To: Wang, YuanX <yuanx.wang@intel.com>; Zhang, Yuying
>> <yuying.zhang@intel.com>
>> Cc: dev@dpdk.org; Ding, Xuan <xuan.ding@intel.com>; Tang, Yaqi
>> <yaqi.tang@intel.com>
>> Subject: Re: [PATCH] app/testpmd: remove useless check
>>
>> Thanks for the patch Yuan.
>>
>> On 10/12/2022 7:59 PM, Yuan Wang wrote:
>>> Protocol header sequence checking is supported in the ethdev library,
>>> the application does not need to do it again.
>>
>> I would like to rephrase the patch title to make it more specific.
>> Like "remove useless check" to "remove unused parameter in rx hdr split"
>> or something like that, to specify the patch.
>
> Thank you for the correction, please feel free to fix when merging.
>
> Thanks,
> Yuan
Done
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-10-17 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 14:29 Yuan Wang
2022-10-14 9:37 ` Singh, Aman Deep
2022-10-14 9:52 ` Wang, YuanX
2022-10-17 8:36 ` Andrew Rybchenko [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=e07835f6-2370-60d9-bcfe-714326537673@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=xuan.ding@intel.com \
--cc=yaqi.tang@intel.com \
--cc=yuanx.wang@intel.com \
--cc=yuying.zhang@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).