From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pci: fix build on FreeBSD
Date: Mon, 03 Aug 2015 17:51:25 +0200 [thread overview]
Message-ID: <34280323.NGXaHzjUp7@xps13> (raw)
In-Reply-To: <1438263693-24165-1-git-send-email-thomas.monjalon@6wind.com>
2015-07-30 15:41, Thomas Monjalon:
> Build log:
> lib/librte_eal/bsdapp/eal/eal_pci.c:462:9: error:
> incompatible integer to pointer conversion passing 'u_int32_t'
> (aka 'unsigned int') to parameter of type 'void *'
>
> It is fixed by passing the pointer of pi.pi_data to memcpy.
>
> By the way, it seems strange that pi_data is initialized twice:
> .pi_data = *(u_int32_t *)buf
> memcpy(&pi.pi_data, buf, len);
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied
prev parent reply other threads:[~2015-08-03 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:41 Thomas Monjalon
2015-08-03 15:49 ` Thomas Monjalon
2015-08-03 15:51 ` 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=34280323.NGXaHzjUp7@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).