From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com
Subject: Re: [dpdk-dev] [PATCH] mbuf: properly cast shared data
Date: Fri, 18 May 2018 13:24:37 +0200 [thread overview]
Message-ID: <1600588.rlgGAYoWKD@xps> (raw)
In-Reply-To: <1526469040-20860-1-git-send-email-david.marchand@6wind.com>
16/05/2018 13:10, David Marchand:
> Including rte_mbuf.h in C++ triggers the following warning as C++ does not
> allow implicit casting of a void *.
>
> In file included from test.cpp:1:0:
> x86_64-native-linuxapp-gcc/include/rte_mbuf.h: In function
> ‘rte_mbuf_ext_shared_info* rte_pktmbuf_ext_shinfo_init_helper(void*, uint16_t*,
> rte_mbuf_extbuf_free_callback_t, void*)’:
> x86_64-native-linuxapp-gcc/include/rte_mbuf.h:1349:9: error: invalid conversion
> from ‘void*’ to ‘rte_mbuf_ext_shared_info*’ [-fpermissive]
> shinfo = RTE_PTR_ALIGN_FLOOR(RTE_PTR_SUB(buf_end,
> ^
>
> Fixes: a53aa2b9f3be ("mbuf: support attaching external buffer")
> Signed-off-by: David Marchand <david.marchand@6wind.com>
Applied, thanks
prev parent reply other threads:[~2018-05-18 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 11:10 David Marchand
2018-05-18 11:24 ` Thomas Monjalon [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=1600588.rlgGAYoWKD@xps \
--to=thomas@monjalon.net \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@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).