From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "zhangwqh@126.com" <zhangwqh@126.com>,
Dhananjaya Eadala <edreddy@gmail.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Qiu, Michael" <michael.qiu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process environment
Date: Thu, 24 Mar 2016 14:00:08 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8CFA80@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <63a15ce2.10cc.15377cbc47b.Coremail.zhangwqh@126.com>
Hi,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ??
> Sent: Tuesday, March 15, 2016 1:03 AM
> To: Dhananjaya Eadala
> Cc: Richardson, Bruce; De Lara Guarch, Pablo; Qiu, Michael; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-
> process environment
>
> Thanks so much for your patch! Your patch exactly solves my bug. :)
I just sent an alternative patch to solve the issue, without requiring #ifdefs.
Could you take a look at it and check that works for you?
Thanks,
Pablo
next prev parent reply other threads:[~2016-03-24 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 2:16 Dhana Eadala
2016-03-14 2:30 ` 张伟
2016-03-14 4:38 ` 张伟
2016-03-15 0:57 ` Dhananjaya Eadala
2016-03-15 1:02 ` 张伟
2016-03-24 14:00 ` De Lara Guarch, Pablo [this message]
2016-04-01 13:14 ` Thomas Monjalon
2016-03-22 11:42 ` Thomas Monjalon
2016-03-22 19:53 ` De Lara Guarch, Pablo
2016-04-19 4:58 ` [dpdk-dev] rte_hash_del_key crash " 张伟
2016-04-19 7:39 ` De Lara Guarch, Pablo
2016-04-19 21:12 ` 张伟
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 3:35 [dpdk-dev] [PATCH] hash: fix memcmp function pointer " Dhana Eadala
2016-03-03 5:44 ` Qiu, Michael
2016-03-04 1:00 ` Dhananjaya Reddy Eadala
2016-03-09 21:36 ` Dhananjaya Reddy Eadala
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=E115CCD9D858EF4F90C690B0DCB4D8973C8CFA80@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=edreddy@gmail.com \
--cc=michael.qiu@intel.com \
--cc=zhangwqh@126.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).