From: Ferruh Yigit <ferruh.yigit@intel.com>
To: eugeny.parshutin@linux.intel.com, thomas@monjalon.net,
john.mcnamara@intel.com
Cc: dev@dpdk.org, roman.p.khatko@intel.com
Subject: Re: [dpdk-dev] [PATCH v4] ethdev: fix for compiler warning when vtune profiling is on
Date: Fri, 3 Apr 2020 18:12:07 +0100 [thread overview]
Message-ID: <94c0aa6e-7894-4415-bc05-d88bf7e0de25@intel.com> (raw)
In-Reply-To: <20200402184516.27033-1-eugeny.parshutin@linux.intel.com>
On 4/2/2020 7:45 PM, eugeny.parshutin@linux.intel.com wrote:
> From: Eugeny Parshutin <eugeny.parshutin@linux.intel.com>
>
> Add the previous prototype for the 'profile_hook_rx_burst_cb' function
> to fix the compiler warning when the DPDK is built with
> 'RTE_ETHDEV_PROFILE_WITH_VTUNE' config option enabled:
> /home/dpdk/lib/librte_ethdev/ethdev_profile.c:17:1: warning:
> no previous prototype for profile_hook_rx_burst_cb [-Wmissing-prototypes]
>
> Fixes: 2c1bbab7f09d ("ethdev: change vtune profiling approach")
> Cc: ilia.kurakin@intel.com
Hi Eugeny,
Thanks for the fix.
Can you please add the "Cc: stable@dpdk.org" tag just below the Fixes line, this
to request backporting the fix to stable trees, which is required for this case
since this is a build fix.
>
> Signed-off-by: Eugeny Parshutin <eugeny.parshutin@linux.intel.com>
> ---
> v2: Fix the commit message
>
> v3: Fix the check-git-log.sh warnings:
> - make headline shorter
> - add 'Fixes' tag
>
> v4: Adapt 'Fixes' section to commit message guidelines
> ---
> lib/librte_ethdev/ethdev_profile.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/lib/librte_ethdev/ethdev_profile.h b/lib/librte_ethdev/ethdev_profile.h
> index 65031e6f3..b8c3c6848 100644
> --- a/lib/librte_ethdev/ethdev_profile.h
> +++ b/lib/librte_ethdev/ethdev_profile.h
> @@ -24,4 +24,14 @@
> int
> __rte_eth_dev_profile_init(uint16_t port_id, struct rte_eth_dev *dev);
>
> +#ifdef RTE_ETHDEV_PROFILE_WITH_VTUNE
> +
> +uint16_t
> +profile_hook_rx_burst_cb(
minor comment, but can you please don't end the line with open parenthesis, '(',
but continue the param list in above line. (I am aware this is how done while
calling the function, but better to fix here.)
> + __rte_unused uint16_t port_id, __rte_unused uint16_t queue_id,
'__rte_unused' tag is not required in the function deceleration, can you please
remove them.
> + __rte_unused struct rte_mbuf *pkts[], uint16_t nb_pkts,
> + __rte_unused uint16_t max_pkts, __rte_unused void *user_param);
> +
> +#endif /* RTE_ETHDEV_PROFILE_WITH_VTUNE */
> +
> #endif
>
prev parent reply other threads:[~2020-04-03 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:45 eugeny.parshutin
2020-04-03 17:12 ` Ferruh Yigit [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=94c0aa6e-7894-4415-bc05-d88bf7e0de25@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=eugeny.parshutin@linux.intel.com \
--cc=john.mcnamara@intel.com \
--cc=roman.p.khatko@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).