From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jeff Guo <jia.guo@intel.com>,
bruce.richardson@intel.com, thomas@monjalon.net
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] eal/bsd: fix FreeBSD build
Date: Tue, 16 Oct 2018 13:38:57 +0100 [thread overview]
Message-ID: <18236da2-c305-d03a-c877-9704e88b34d9@intel.com> (raw)
In-Reply-To: <7ce45d10-71d3-5788-6124-3ee6a4c59288@intel.com>
On 10/16/2018 1:04 PM, Ferruh Yigit wrote:
> On 10/16/2018 12:41 PM, Jeff Guo wrote:
>> When compiling on FreeBSD, a warning/error is thrown for
>> unused parameter. This patch aim to fix the issue by delete
>> the useless func definition.
>
> This function is part of the public API, so it should exist for FreeBSD, I think
> instead of deleting the function we can add __rte_unused to parameters that are
> not used to prevent build error.
With second check, rte_dev_event_callback_process() seems already implemented in
common, lib/librte_eal/common/eal_common_dev.c, and doesn't need linux/bsd
specific implementation, so adding this to bsdapp seems error at first place.
OK to remove function.
Fixes: 89ecd110524d ("eal: modify device event process function")
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
>>
>> Signed-off-by: Jeff Guo <jia.guo@intel.com>
>> ---
>> lib/librte_eal/bsdapp/eal/eal_dev.c | 8 --------
>> 1 file changed, 8 deletions(-)
>>
>> diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
>> index 3a3a2a5..255d611 100644
>> --- a/lib/librte_eal/bsdapp/eal/eal_dev.c
>> +++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
>> @@ -33,11 +33,3 @@ rte_dev_hotplug_handle_disable(void)
>> RTE_LOG(ERR, EAL, "Device event is not supported for FreeBSD\n");
>> return -1;
>> }
>> -
>> -void __rte_experimental
>> -rte_dev_event_callback_process(const char *device_name,
>> - enum rte_dev_event_type event)
>> -{
>> - RTE_LOG(ERR, EAL,
>> - "Device event callback process is not supported for FreeBSD.\n");
>> -}
>>
>
next prev parent reply other threads:[~2018-10-16 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 11:41 Jeff Guo
2018-10-16 12:04 ` Ferruh Yigit
2018-10-16 12:38 ` Ferruh Yigit [this message]
2018-10-18 8:09 ` Burakov, Anatoly
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=18236da2-c305-d03a-c877-9704e88b34d9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=thomas@monjalon.net \
/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).