DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: <dev@dpdk.org>, <thomas@monjalon.net>
Cc: <ferruh.yigit@intel.com>, <shreyansh.jain@nxp.com>,
	<akhil.goyal@nxp.com>
Subject: [dpdk-dev] [PATCH 3/8] bus/fslmc: fixes compilation in debug mode
Date: Tue, 11 Jul 2017 20:25:54 +0530	[thread overview]
Message-ID: <1499784959-8598-4-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1499784959-8598-1-git-send-email-hemant.agrawal@nxp.com>

Fixes: 9ccb76b24c1d ("bus/fslmc: enable portal interrupt handling")

Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
 drivers/bus/fslmc/portal/dpaa2_hw_dpio.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c b/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
index 88dd2e9..5cf5cfe 100644
--- a/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
+++ b/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
@@ -122,7 +122,7 @@ static void dpaa2_affine_dpio_intr_to_respective_core(int32_t dpio_id)
 	snprintf(string, STRING_LEN, "dpio.%d", dpio_id);
 	file = fopen("/proc/interrupts", "r");
 	if (!file) {
-		PMD_DRV_LOG(WARN, "Failed to open /proc/interrupts file\n");
+		PMD_DRV_LOG(WARNING, "Failed to open /proc/interrupts file\n");
 		return;
 	}
 	while (getline(&temp, &len, file) != -1) {
@@ -133,7 +133,7 @@ static void dpaa2_affine_dpio_intr_to_respective_core(int32_t dpio_id)
 	}
 
 	if (!token) {
-		PMD_DRV_LOG(WARN, "Failed to get interrupt id for dpio.%d\n",
+		PMD_DRV_LOG(WARNING, "Failed to get interrupt id for dpio.%d\n",
 			    dpio_id);
 		if (temp)
 			free(temp);
@@ -146,10 +146,10 @@ static void dpaa2_affine_dpio_intr_to_respective_core(int32_t dpio_id)
 		 cpu_mask, token);
 	ret = system(command);
 	if (ret < 0)
-		PMD_DRV_LOG(WARN,
+		PMD_DRV_LOG(WARNING,
 			"Failed to affine interrupts on respective core\n");
 	else
-		PMD_DRV_LOG(WARN, " %s command is executed\n", command);
+		PMD_DRV_LOG(WARNING, " %s command is executed\n", command);
 
 	free(temp);
 	fclose(file);
-- 
2.7.4

  parent reply	other threads:[~2017-07-11 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 14:55 [dpdk-dev] [PATCH 0/8] NXP DPAA2 compilation and runtime fixes Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 1/8] crypto/dpaa2_sec: remove GCC 7.1 compilation error Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 2/8] net/dpaa2: fix flow control switch case break Hemant Agrawal
2017-07-11 14:55 ` Hemant Agrawal [this message]
2017-07-11 14:55 ` [dpdk-dev] [PATCH 4/8] event/dpaa2: enable debug mode compilation Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 5/8] bus/fslmc: set the dpaa2 device name Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 6/8] bus/fslmc: align the object name log to real resource names Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 7/8] config: enable virtual IOVA by default for DPAA2 Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 8/8] drivers: add newline in RTE LOG usages in dpaa2 Hemant Agrawal
2017-07-14 13:49 ` [dpdk-dev] [PATCH 0/8] NXP DPAA2 compilation and runtime fixes 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=1499784959-8598-4-git-send-email-hemant.agrawal@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shreyansh.jain@nxp.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).