DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/6] librte_log: add function to retrieve log_level
Date: Fri, 13 Nov 2015 14:04:02 -0500	[thread overview]
Message-ID: <20151113190402.GD25051@mhcomputing.net> (raw)
In-Reply-To: <4536748.1MnZAysZE1@xps13>

On Fri, Nov 13, 2015 at 12:49:36PM +0100, Thomas Monjalon wrote:
> I'm sad for you Bruce: you only see an empty line where you could catch
> the beauty of the star ;)

+1

> Matthew, obviously you failed your send.

You might find a more polite way than calling contributions failures. ;)

> As a general comment, please group patches by logic meaning and
> check them before sending ;)

I did. But I'm a community guy and this is not full-time employment, and I am 
admittedly quite bad at git email workflow and don't like it much as discussed 
in previous threads.

So I did the best I could do but screwed up something minor at approx 1 or 2 
AM. It happens. I don't send you guys crazy emails when there is a build 
failure upstream either you know. (:

Matthew.

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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  6:47 [dpdk-dev] [PATCH 0/6] librte_eal: allow wider range of log levels Matthew Hall
2015-11-13  6:47 ` [dpdk-dev] [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 [this message]
2015-11-13 19:01     ` Matthew Hall
2015-11-13  6:47 ` [dpdk-dev] [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 ` [dpdk-dev] [PATCH 3/6] eal_common_log.c: reset default level to RTE_LOG_FINEST Matthew Hall
2015-11-13  6:47 ` [dpdk-dev] [PATCH 4/6] rte_log.h: update logging docs to include FINEST level Matthew Hall
2015-11-13  6:47 ` [dpdk-dev] [PATCH 5/6] rte_log.h: add RTE_SYSLOG_LEVEL_MAX Matthew Hall
2015-11-13  6:47 ` [dpdk-dev] [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=20151113190402.GD25051@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).