DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: alejandro.lucero@netronome.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/5] net/nfp logging fixes
Date: Wed, 25 Apr 2018 08:45:46 -0700	[thread overview]
Message-ID: <20180425154551.6795-1-stephen@networkplumber.org> (raw)

These are several small changes to make the Netronome driver
use logging macros in the same way as other drivers.

Compile tested only. I don't have Netronome hardware.

Stephen Hemminger (5):
  net/nfp: use correct logtype for init messages
  net/nfp: add implied new line to PMD_DRV_LOG
  net/nfp: fix double space in init log
  net/nfl: add newline in PMD_RX/TX_LOG macros
  net/nfp: use dynamic logging everywhere

 drivers/net/nfp/nfp_net.c      | 186 ++++++++++++++++-----------------
 drivers/net/nfp/nfp_net_logs.h |   9 +-
 2 files changed, 98 insertions(+), 97 deletions(-)

-- 
2.17.0

             reply	other threads:[~2018-04-25 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 15:45 Stephen Hemminger [this message]
2018-04-25 15:45 ` [dpdk-dev] [PATCH 1/5] net/nfp: use correct logtype for init messages Stephen Hemminger
2018-04-25 15:45 ` [dpdk-dev] [PATCH 2/5] net/nfp: add implied new line to PMD_DRV_LOG Stephen Hemminger
2018-04-25 15:45 ` [dpdk-dev] [PATCH 3/5] net/nfp: fix double space in init log Stephen Hemminger
2018-04-25 15:45 ` [dpdk-dev] [PATCH 4/5] net/nfl: add newline in PMD_RX/TX_LOG macros Stephen Hemminger
2018-04-25 15:45 ` [dpdk-dev] [PATCH 5/5] net/nfp: use dynamic logging everywhere Stephen Hemminger
2018-04-26 12:52 ` [dpdk-dev] [PATCH 0/5] net/nfp logging fixes Alejandro Lucero
2018-04-26 15:42   ` Stephen Hemminger
2018-04-26 18:14     ` Alejandro Lucero
2018-04-26 21:52       ` 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=20180425154551.6795-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=alejandro.lucero@netronome.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).