From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/test-crypto-perf: fix missing bounds check on socket id
Date: Tue, 9 Apr 2019 10:24:17 +0000 [thread overview]
Message-ID: <302b2e19-d81b-45d6-8b2f-807a05e65584@email.android.com> (raw)
Message-ID: <20190409102417.Bs19uXCHoUzZH90kDHfy38TlFUKuqASnKI3Tf8aGapc@z> (raw)
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Respond through mobile, sorry for any funny formatting/font may exist in this email.
next reply other threads:[~2019-04-09 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 10:24 Zhang, Roy Fan [this message]
2019-04-09 10:24 ` Zhang, Roy Fan
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 9:25 Bruce Richardson
2019-04-08 9:25 ` Bruce Richardson
2019-04-16 13:49 ` Akhil Goyal
2019-04-16 13:49 ` Akhil Goyal
2019-04-16 15:00 ` Akhil Goyal
2019-04-16 15:00 ` Akhil Goyal
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=302b2e19-d81b-45d6-8b2f-807a05e65584@email.android.com \
--to=roy.fan.zhang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).