From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 0/6] log de-spamming Date: Thu, 30 Jul 2015 20:18:23 +0200 Message-ID: <2377667.tsNWiATpWU@xps13> References: <1436482868-7400-1-git-send-email-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Stephen Hemminger To: Stephen Hemminger Return-path: Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by dpdk.org (Postfix) with ESMTP id A9842C6BE for ; Thu, 30 Jul 2015 20:23:09 +0200 (CEST) Received: by wibud3 with SMTP id ud3so2967934wib.0 for ; Thu, 30 Jul 2015 11:23:09 -0700 (PDT) In-Reply-To: <1436482868-7400-1-git-send-email-stephen@networkplumber.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-07-09 16:01, Stephen Hemminger: > From: Stephen Hemminger > > 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