DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 4/6] rte_log.h: update logging docs to include FINEST level
Date: Fri, 13 Nov 2015 06:47:36 +0000	[thread overview]
Message-ID: <1447397258-27233-5-git-send-email-mhall@mhcomputing.net> (raw)
In-Reply-To: <1447397258-27233-1-git-send-email-mhall@mhcomputing.net>

Signed-off-by: Matthew Hall <mhall@mhcomputing.net>
---
 lib/librte_eal/common/include/rte_log.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lib/librte_eal/common/include/rte_log.h b/lib/librte_eal/common/include/rte_log.h
index 7dc19e1..4a70ce5 100644
--- a/lib/librte_eal/common/include/rte_log.h
+++ b/lib/librte_eal/common/include/rte_log.h
@@ -128,7 +128,7 @@ int rte_openlog_stream(FILE *f);
  * displayed.
  *
  * @param level
- *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_DEBUG (8).
+ *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_FINEST (11).
  */
 void rte_set_log_level(uint32_t level);
 
@@ -228,7 +228,7 @@ int rte_log_add_in_history(const char *buf, size_t size);
  * logs are automatically prefixed by type when using the macro.
  *
  * @param level
- *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_DEBUG (8).
+ *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_FINEST (11).
  * @param logtype
  *   The log type, for example, RTE_LOGTYPE_EAL.
  * @param format
@@ -260,7 +260,7 @@ int rte_log(uint32_t level, uint32_t logtype, const char *format, ...)
  * removed at compilation time.
  *
  * @param level
- *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_DEBUG (8).
+ *   Log level. A value between RTE_LOG_EMERG (1) and RTE_LOG_FINEST (11).
  * @param logtype
  *   The log type, for example, RTE_LOGTYPE_EAL.
  * @param format
@@ -289,7 +289,7 @@ int rte_vlog(uint32_t level, uint32_t logtype, const char *format, va_list ap)
  *   RTE_LOG(INFO, EAL, "this is a %s", "log");
  *
  * @param l
- *   Log level. A value between EMERG (1) and DEBUG (8). The short name is
+ *   Log level. A value between EMERG (1) and FINEST (11). The short name is
  *   expanded by the macro, so it cannot be an integer value.
  * @param t
  *   The log type, for example, EAL. The short name is expanded by the
-- 
1.9.1

  parent reply	other threads:[~2015-11-13  6:48 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
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 ` Matthew Hall [this message]
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=1447397258-27233-5-git-send-email-mhall@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).