From: "Liang, Cunming" <cunming.liang@intel.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] virtio: Fix compilation issue on freebsd
Date: Fri, 27 Feb 2015 05:11:31 +0000 [thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA3118DF6F0@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1425004210-4044-1-git-send-email-changchun.ouyang@intel.com>
Hi,
> -----Original Message-----
> From: Ouyang, Changchun
> Sent: Friday, February 27, 2015 10:30 AM
> To: dev@dpdk.org
> Cc: Liang, Cunming; Cao, Waterman; Ouyang, Changchun
> Subject: [PATCH] virtio: Fix compilation issue on freebsd
>
> This patch fixes the compilation issue on freebsd:
>
> /root/qwan/tmp/dpdk_org/lib/librte_pmd_virtio/virtio_ethdev.c: In function
> 'virtio_resource_init':
> /root/qwan/tmp/dpdk_org/lib/librte_pmd_virtio/virtio_ethdev.c:1071:56: error:
> unused parameter 'pci_dev' [-Werror=unused-parameter] static int
> virtio_resource_init(struct rte_pci_device *pci_dev)
> ^
> cc1: all warnings being treated as errors
>
> Signed-off-by: Changchun Ouyang <changchun.ouyang@intel.com>
> ---
> lib/librte_pmd_virtio/virtio_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_pmd_virtio/virtio_ethdev.c
> b/lib/librte_pmd_virtio/virtio_ethdev.c
> index 9eb0217..88ecd57 100644
> --- a/lib/librte_pmd_virtio/virtio_ethdev.c
> +++ b/lib/librte_pmd_virtio/virtio_ethdev.c
> @@ -1068,7 +1068,7 @@ virtio_has_msix(const struct rte_pci_addr *loc
> __rte_unused)
> return 0;
> }
>
> -static int virtio_resource_init(struct rte_pci_device *pci_dev)
> +static int virtio_resource_init(struct rte_pci_device *pci_dev __rte_unused)
> {
> /* no setup required */
> return 0;
> --
> 1.8.4.2
Acked-by: Cunming Liang <cunming.liang@intel.com>
next prev parent reply other threads:[~2015-02-27 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 2:30 Ouyang Changchun
2015-02-27 5:11 ` Liang, Cunming [this message]
2015-02-27 23:13 ` Thomas Monjalon
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=D0158A423229094DA7ABF71CF2FA0DA3118DF6F0@shsmsx102.ccr.corp.intel.com \
--to=cunming.liang@intel.com \
--cc=changchun.ouyang@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).