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 v5] ethdev: fix for compiler warning when vtune profiling is on
Date: Tue, 7 Apr 2020 11:26:36 +0100 [thread overview]
Message-ID: <2b4743de-5144-6e07-7717-a7f022d9486b@intel.com> (raw)
In-Reply-To: <20200406182705.11190-1-eugeny.parshutin@linux.intel.com>
On 4/6/2020 7:27 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: stable@dpdk.org
>
> Signed-off-by: Eugeny Parshutin <eugeny.parshutin@linux.intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-04-07 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 18:27 eugeny.parshutin
2020-04-07 10:26 ` 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=2b4743de-5144-6e07-7717-a7f022d9486b@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).