From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/6] log de-spamming
Date: Thu, 30 Jul 2015 20:18:23 +0200 [thread overview]
Message-ID: <2377667.tsNWiATpWU@xps13> (raw)
In-Reply-To: <1436482868-7400-1-git-send-email-stephen@networkplumber.org>
2015-07-09 16:01, Stephen Hemminger:
> From: Stephen Hemminger <shemming@brocade.com>
>
> These patches were sent earlier, updated to current tree.
>
> They make Intel drivers not spam the log with information
> messages that cause questions in production.
>
> Unfortunately, developers seem to get attached to log messages
> which are not appropriate in a production product
>
> Stephen Hemminger (6):
> ixgbe: convert debug messages to DEBUG level
> ixgbe: raise priority of significant log events
> ixgbe: allow pruning log during build
> e1000: allow pruning log during build
> e1000: change log level of debug messages
> e1000: raise log level of signifcant events
Applied, thanks
prev parent reply other threads:[~2015-07-30 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 23:01 Stephen Hemminger
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 1/6] ixgbe: convert debug messages to DEBUG level Stephen Hemminger
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 2/6] ixgbe: raise priority of significant log events Stephen Hemminger
2015-07-09 23:27 ` Thomas Monjalon
2015-07-09 23:39 ` Stephen Hemminger
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 3/6] ixgbe: allow pruning log during build Stephen Hemminger
2015-07-09 23:28 ` Thomas Monjalon
2015-07-30 17:31 ` Thomas Monjalon
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 4/6] e1000: " Stephen Hemminger
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 5/6] e1000: change log level of debug messages Stephen Hemminger
2015-07-09 23:01 ` [dpdk-dev] [PATCH v3 6/6] e1000: raise log level of signifcant events Stephen Hemminger
2015-07-30 18:18 ` Thomas Monjalon [this message]
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=2377667.tsNWiATpWU@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=stephen@networkplumber.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).