DPDK patches and discussions
 help / color / mirror / Atom feed
From: Avi Kivity <avi@cloudius-systems.com>
To: Olivier MATZ <olivier.matz@6wind.com>, thomas.monjalon@6wind.com
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mempool: fix incompatibility with C++ in header file
Date: Mon, 17 Aug 2015 11:40:14 +0300	[thread overview]
Message-ID: <55D19DEE.8060404@cloudius-systems.com> (raw)
In-Reply-To: <55D19C6F.3040501@6wind.com>

(adding list+Thomas back to cc)

On 08/17/2015 11:33 AM, Olivier MATZ wrote:
> Hi,
>
> On 08/14/2015 10:33 AM, Avi Kivity wrote:
>> C++ doesn't allow implied casting from void * to another pointer, so
>> supply an explicit cast.
>>
>> Signed-off-by: Avi Kivity <avi@cloudius-systems.com>
> For Thomas:
> This fix is already submitted in
> http://dpdk.org/dev/patchwork/patch/6750/
>
>
> Thanks Avi

      parent reply	other threads:[~2015-08-17  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14  8:33 Avi Kivity
     [not found] ` <55D19C6F.3040501@6wind.com>
2015-08-17  8:40   ` Avi Kivity [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=55D19DEE.8060404@cloudius-systems.com \
    --to=avi@cloudius-systems.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=thomas.monjalon@6wind.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).