From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 4/9] net/bnx2x: remove redundant EOL char from logs
Date: Fri, 27 Jan 2017 17:46:14 +0000 [thread overview]
Message-ID: <20170127174619.23585-4-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20170127174619.23585-1-ferruh.yigit@intel.com>
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
drivers/net/bnx2x/bnx2x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/bnx2x/bnx2x.c b/drivers/net/bnx2x/bnx2x.c
index 0d16a73..cc380bd 100644
--- a/drivers/net/bnx2x/bnx2x.c
+++ b/drivers/net/bnx2x/bnx2x.c
@@ -2220,7 +2220,7 @@ int bnx2x_tx_encap(struct bnx2x_tx_queue *txq, struct rte_mbuf *m0)
}
PMD_TX_LOG(DEBUG,
- "start bd: nbytes %d flags %x vlan %x\n",
+ "start bd: nbytes %d flags %x vlan %x",
tx_start_bd->nbytes,
tx_start_bd->bd_flags.as_bitfield,
tx_start_bd->vlan_or_ethertype);
--
2.9.3
next prev parent reply other threads:[~2017-01-27 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 17:46 [dpdk-dev] [PATCH 1/9] net/ixgbe: remove redundant EOL character " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 2/9] net/i40e: remove redundant EOL char " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 3/9] net/e1000: " Ferruh Yigit
2017-01-27 17:46 ` Ferruh Yigit [this message]
2017-01-27 17:46 ` [dpdk-dev] [PATCH 5/9] net/ena: " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 6/9] net/nfp: " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 7/9] net/qede: " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 8/9] net/sfc: " Ferruh Yigit
2017-01-27 17:46 ` [dpdk-dev] [PATCH 9/9] net/virtio: " Ferruh Yigit
2017-01-27 17:49 ` [dpdk-dev] [PATCH 1/9] net/ixgbe: remove redundant EOL character " Stephen Hemminger
2017-01-30 10:35 ` 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=20170127174619.23585-4-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@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).