DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] librte_log: add function to retrieve log_level
Date: Sun, 14 Sep 2014 01:36:09 -0700	[thread overview]
Message-ID: <20140914083609.GA23464@mhcomputing.net> (raw)
In-Reply-To: <1410683686-12389-1-git-send-email-mhall@mhcomputing.net>

On Sun, Sep 14, 2014 at 01:34:46AM -0700, Matthew Hall wrote:
> Signed-off-by: Matthew Hall <mhall@mhcomputing.net>
> ---
>  lib/librte_eal/common/eal_common_log.c  | 7 +++++++
>  lib/librte_eal/common/include/rte_log.h | 6 ++++++
>  2 files changed, 13 insertions(+)

I forgot to mention in the comments, this patch is helpful when you want 
outside code to cooperate with and respect log levels set in DPDK. Then you 
can avoid using duplicate incompatible log code in the DPDK and non-DPDK parts 
of the app.

Matthew.

  reply	other threads:[~2014-09-14  8:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14  8:34 Matthew Hall
2014-09-14  8:36 ` Matthew Hall [this message]
2014-09-15  8:14 ` Richardson, Bruce
2014-09-15  8:16   ` Matthew Hall
2014-09-15  8:20     ` Richardson, Bruce
2014-09-15  8:24       ` Matthew Hall
2014-09-18 13:29   ` Thomas Monjalon
2014-09-18 20:25     ` 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=20140914083609.GA23464@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --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).