From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, <dev@dpdk.org>
Cc: <jerin.jacob@caviumnetworks.com>, <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 2/5] bus/dpaa: fix unused function warning with clang
Date: Tue, 30 Jan 2018 11:50:30 +0530 [thread overview]
Message-ID: <95b3a4b0-b6db-74f5-748b-d4f7342296a0@nxp.com> (raw)
In-Reply-To: <1516874011-8760-3-git-send-email-hemant.agrawal@nxp.com>
On Thursday 25 January 2018 03:23 PM, Hemant Agrawal wrote:
> fman/netcfg_layer.c:80:1: error: unused function 'get_num_netcfg_interfaces
> ' [-Werror,-Wunused-function] get_num_netcfg_interfaces(char *str)
>
> Fixes: 919eeaccb2ba ("bus/dpaa: introduce NXP DPAA bus driver skeleton")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
Acked-By: Shreyansh Jain <shreyansh.jain@nxp.com>
next prev parent reply other threads:[~2018-01-30 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1516874011-8760-1-git-send-email-hemant.agrawal@nxp.com>
2018-01-25 9:53 ` [dpdk-stable] [PATCH 1/5] bus/dpaa: fix compilation warnings " Hemant Agrawal
2018-01-30 6:19 ` Shreyansh Jain
2018-01-25 9:53 ` [dpdk-stable] [PATCH 2/5] bus/dpaa: fix unused function warning " Hemant Agrawal
2018-01-30 6:20 ` Shreyansh Jain [this message]
2018-01-25 9:53 ` [dpdk-stable] [PATCH 3/5] crypto/dpaa2_sec: fix enum conversion for GCM Hemant Agrawal
2018-01-25 9:53 ` [dpdk-stable] [PATCH 4/5] crypto/dpaa_sec: " Hemant Agrawal
2018-01-23 7:52 [dpdk-stable] [PATCH 1/5] bus/dpaa: fix compilation warnings with clang Hemant Agrawal
2018-01-23 7:52 ` [dpdk-stable] [PATCH 2/5] bus/dpaa: fix unused function warning " Hemant Agrawal
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=95b3a4b0-b6db-74f5-748b-d4f7342296a0@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@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).