patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
	"Liu, Mingxia" <mingxia.liu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Li, Xiaoyun" <xiaoyun.li@intel.com>,
	"Singh, Aman Deep" <aman.deep.singh@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] app/testpmd: change a magic number to macro
Date: Fri, 20 May 2022 23:09:40 +0100	[thread overview]
Message-ID: <b47ce6d9-bb38-d1b1-2f74-45a4d1c70bca@amd.com> (raw)
In-Reply-To: <DM6PR11MB3516140DF031C0CA5B3FF6508EE09@DM6PR11MB3516.namprd11.prod.outlook.com>

On 4/1/2022 9:50 AM, Zhang, Yuying wrote:
> Hi Mingxia,
> 
> LGTM.
> 
>> -----Original Message-----
>> From: Liu, Mingxia <mingxia.liu@intel.com>
>> Sent: Thursday, March 31, 2022 10:34 AM
>> To: dev@dpdk.org
>> Cc: Li, Xiaoyun <xiaoyun.li@intel.com>; Singh, Aman Deep
>> <aman.deep.singh@intel.com>; Zhang, Yuying <yuying.zhang@intel.com>;
>> Liu, Mingxia <mingxia.liu@intel.com>; stable@dpdk.org
>> Subject: [PATCH v2] app/testpmd: change a magic number to macro
>>
>> From: mingxial <mingxia.liu@intel.com>
>>
>> Add macro MIN_TOTAL_NUM_MBUFS (1024) to indicate what the value of
>> total-num-mbufs should bigger than.
>>
>> Fixes: c87988187fdb ("app/testpmd: add --total-num-mbufs option")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: mingxial <mingxia.liu@intel.com>
> 
> Acked-by: Yuying Zhang <yuying.zhang@intel.com>
> 

Updated sign off as:
Signed-off-by: Mingxia Liu <mingxia.liu@intel.com>

Acked-by: Ferruh Yigit <ferruh.yigit@xilinx.com>

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2022-05-20 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  7:14 [PATCH v1] app/test-pmd: " Mingxia Liu
2022-03-31  2:33 ` [PATCH v2] app/testpmd: " Mingxia Liu
2022-04-01  8:50   ` Zhang, Yuying
2022-05-20 22:09     ` Ferruh Yigit [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=b47ce6d9-bb38-d1b1-2f74-45a4d1c70bca@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=mingxia.liu@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiaoyun.li@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).