patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: bruce.richardson@intel.com, reshma.pattan@intel.com,
	Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH 18.11 2/3] bus/fslmc: fix warning with GCC 9
Date: Thu, 16 May 2019 19:21:56 +0100	[thread overview]
Message-ID: <20190516182157.32128-3-ktraynor@redhat.com> (raw)
In-Reply-To: <20190516182157.32128-1-ktraynor@redhat.com>

Printing a null pointer with %s is flagged as a warning by GCC 9, and
should not be done. Replace the %s with the word "null" itself.

This is an additional GCC 9 fix required for dpdk-stable.

Fixes: 50245be05d1a ("bus/fslmc: support device blacklisting")

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 drivers/bus/fslmc/fslmc_bus.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/bus/fslmc/fslmc_bus.c b/drivers/bus/fslmc/fslmc_bus.c
index 9ee1bf862..776b7caad 100644
--- a/drivers/bus/fslmc/fslmc_bus.c
+++ b/drivers/bus/fslmc/fslmc_bus.c
@@ -253,5 +253,5 @@ rte_fslmc_parse(const char *name, void *addr)
 	t_ptr = strchr(name, '.');
 	if (!t_ptr) {
-		DPAA2_BUS_ERR("Incorrect device string observed (%s)", t_ptr);
+		DPAA2_BUS_ERR("Incorrect device string observed (null)");
 		goto err_out;
 	}
-- 
2.20.1


  parent reply	other threads:[~2019-05-16 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 18:21 [dpdk-stable] [PATCH 18.11 0/3] Fixes for " Kevin Traynor
2019-05-16 18:21 ` [dpdk-stable] [PATCH 18.11 1/3] mk: disable warning for packed member pointer Kevin Traynor
2019-05-16 18:21 ` Kevin Traynor [this message]
2019-05-16 18:21 ` [dpdk-stable] [PATCH 18.11 3/3] mk: disable packed member pointer warning for telemetry Kevin Traynor
2019-05-17  8:39 ` [dpdk-stable] [PATCH 18.11 0/3] Fixes for GCC 9 Richardson, Bruce
2019-05-20 16:24   ` Kevin Traynor

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=20190516182157.32128-3-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=reshma.pattan@intel.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).