DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tomasz Duszynski <tdu@semihalf.com>
To: dev@dpdk.org
Cc: dima@marvell.com, nsamsono@marvell.com, jck@semihalf.com,
	jianbo.liu@arm.com, Tomasz Duszynski <tdu@semihalf.com>,
	stable@dpdk.org
Subject: [dpdk-dev] [PATCH] net/mrvl: fix typo in log message
Date: Mon, 19 Mar 2018 13:37:22 +0100	[thread overview]
Message-ID: <1521463042-31226-1-git-send-email-tdu@semihalf.com> (raw)

Show appropriate log message in case Tx offloads are either
not supported or missing.

Fixes: 7d8f6c20cc7c ("net/mrvl: switch to the new Tx offload API")
Cc: stable@dpdk.org

Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
---
 drivers/net/mrvl/mrvl_ethdev.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/mrvl/mrvl_ethdev.c b/drivers/net/mrvl/mrvl_ethdev.c
index fac924f..61c1223 100644
--- a/drivers/net/mrvl/mrvl_ethdev.c
+++ b/drivers/net/mrvl/mrvl_ethdev.c
@@ -1700,14 +1700,14 @@ mrvl_tx_queue_offloads_okay(struct rte_eth_dev *dev, uint64_t requested)
 	uint64_t missing = mandatory & ~requested;
 
 	if (unsupported) {
-		RTE_LOG(ERR, PMD, "Some Rx offloads are not supported. "
+		RTE_LOG(ERR, PMD, "Some Tx offloads are not supported. "
 			"Requested 0x%" PRIx64 " supported 0x%" PRIx64 ".\n",
 			requested, supported);
 		return 0;
 	}
 
 	if (missing) {
-		RTE_LOG(ERR, PMD, "Some Rx offloads are missing. "
+		RTE_LOG(ERR, PMD, "Some Tx offloads are missing. "
 			"Requested 0x%" PRIx64 " missing 0x%" PRIx64 ".\n",
 			requested, missing);
 		return 0;
-- 
2.7.4

             reply	other threads:[~2018-03-19 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 12:37 Tomasz Duszynski [this message]
2018-03-20 12:05 ` Ferruh Yigit

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=1521463042-31226-1-git-send-email-tdu@semihalf.com \
    --to=tdu@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=dima@marvell.com \
    --cc=jck@semihalf.com \
    --cc=jianbo.liu@arm.com \
    --cc=nsamsono@marvell.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).