All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/6] librte_log: add function to retrieve log_level
Date: Fri, 13 Nov 2015 14:01:42 -0500	[thread overview]
Message-ID: <20151113190142.GC25051@mhcomputing.net> (raw)
In-Reply-To: <20151113114008.GA15612@bricha3-MOBL3>

On Fri, Nov 13, 2015 at 11:40:09AM +0000, Bruce Richardson wrote:
> I don't think this patch is necessary, as all it adds is a single extra line to
> a comment.
> 
> /Bruce

This one was previously merged. So indeed we can toss it.

This is what happens when you are restricted to 1 AM coding.

Matthew.

  parent reply	other threads:[~2015-11-13 19:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  6:47 [PATCH 0/6] librte_eal: allow wider range of log levels Matthew Hall
2015-11-13  6:47 ` [PATCH 1/6] librte_log: add function to retrieve log_level Matthew Hall
2015-11-13 11:40   ` Bruce Richardson
2015-11-13 11:49     ` Thomas Monjalon
2015-11-13 19:04       ` Matthew Hall
2015-11-13 19:01     ` Matthew Hall [this message]
2015-11-13  6:47 ` [PATCH 2/6] rte_log.h: add detailed log levels RTE_LOG{FINE, FINER, FINEST} Matthew Hall
2015-11-13 11:44   ` Bruce Richardson
2015-11-13 11:48     ` Ananyev, Konstantin
2015-11-13 19:14       ` Matthew Hall
2015-11-13 19:16     ` Matthew Hall
2015-11-13 16:07   ` Stephen Hemminger
2015-11-13 19:15     ` Matthew Hall
2015-11-13  6:47 ` [PATCH 3/6] eal_common_log.c: reset default level to RTE_LOG_FINEST Matthew Hall
2015-11-13  6:47 ` [PATCH 4/6] rte_log.h: update logging docs to include FINEST level Matthew Hall
2015-11-13  6:47 ` [PATCH 5/6] rte_log.h: add RTE_SYSLOG_LEVEL_MAX Matthew Hall
2015-11-13  6:47 ` [PATCH 6/6] eal_log.c: limit syslog level to RTE_SYSLOG_LEVEL_MAX Matthew Hall

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=20151113190142.GC25051@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=bruce.richardson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.