From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal/bsdapp: fix compilation on FreeBSD
Date: Mon, 11 May 2015 15:45:46 +0200 [thread overview]
Message-ID: <1647994.EPP3JTkp5f@xps13> (raw)
In-Reply-To: <1430830054-28791-1-git-send-email-bruce.richardson@intel.com>
> Fixes: 6065355a "pci: make device id tables const"
>
> Following the above commit, compilation on FreeBSD with clang was broken,
> giving the error message:
>
> .../lib/librte_eal/bsdapp/eal/eal_pci.c:438:16: fatal error: assigning to
> 'struct rte_pci_id *' from 'const struct rte_pci_id *' discards qualifiers
> [-Wincompatible-pointer-types-discards-qualifiers]
> for (id_table = dr->id_table ; id_table->vendor_id != 0; id_table++) {
> ^ ~~~~~~~~~~~~
>
> This patch fixes the issue by adding "const" to the type of id_table.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-05-11 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 12:47 Bruce Richardson
2015-05-11 13:45 ` 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=1647994.EPP3JTkp5f@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).