From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Intel driver silence excess logging
Date: Mon, 9 Mar 2015 12:18:33 -0700 [thread overview]
Message-ID: <1425928715-2980-1-git-send-email-stephen@networkplumber.org> (raw)
The Intel drivers seem to be getting more verbose in the log with
each release. This is not a good thing.
Stephen Hemminger (2):
ixgbe: silence noisy log messages
e1000: silence noisy log messages
lib/librte_pmd_e1000/e1000_logs.h | 3 +--
lib/librte_pmd_e1000/em_ethdev.c | 10 ++++------
lib/librte_pmd_e1000/igb_ethdev.c | 12 ++++--------
lib/librte_pmd_ixgbe/ixgbe_ethdev.c | 15 +++++----------
lib/librte_pmd_ixgbe/ixgbe_logs.h | 3 +--
lib/librte_pmd_ixgbe/ixgbe_rxtx.c | 12 ++++++------
6 files changed, 21 insertions(+), 34 deletions(-)
--
2.1.4
next reply other threads:[~2015-03-09 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 19:18 Stephen Hemminger [this message]
2015-03-09 19:18 ` [dpdk-dev] [PATCH 1/2] ixgbe: silence noisy log messages Stephen Hemminger
2015-03-19 11:26 ` David Marchand
2015-03-09 19:18 ` [dpdk-dev] [PATCH 2/2] e1000: " Stephen Hemminger
2015-03-19 11:28 ` David Marchand
2015-03-19 11:31 ` [dpdk-dev] [PATCH 0/2] Intel driver silence excess logging David Marchand
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=1425928715-2980-1-git-send-email-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).