From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: Mingjin Ye <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "qiming.yang@intel.com" <qiming.yang@intel.com>,
"yidingx.zhou@intel.com" <yidingx.zhou@intel.com>,
Cheng Jiang <honest.jiang@foxmail.com>
Subject: RE: [EXT] [PATCH v2] app/dma-perf: fix lcores array out of bounds access
Date: Fri, 27 Oct 2023 14:27:36 +0000 [thread overview]
Message-ID: <CO1PR18MB471463C6E286B8741ED7FEA8CBDCA@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20231026095313.3053665-1-mingjinx.ye@intel.com>
Looks good to me.
Acked-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
next prev parent reply other threads:[~2023-10-27 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 10:09 [PATCH] app/dma-perf: fix dma mapping access overruns Mingjin Ye
2023-10-26 9:53 ` [PATCH v2] app/dma-perf: fix lcores array out of bounds access Mingjin Ye
2023-10-27 14:27 ` Gowrishankar Muthukrishnan [this message]
2023-11-14 14:37 ` Thomas Monjalon
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=CO1PR18MB471463C6E286B8741ED7FEA8CBDCA@CO1PR18MB4714.namprd18.prod.outlook.com \
--to=gmuthukrishn@marvell.com \
--cc=dev@dpdk.org \
--cc=honest.jiang@foxmail.com \
--cc=mingjinx.ye@intel.com \
--cc=qiming.yang@intel.com \
--cc=yidingx.zhou@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).