From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/4] Add severity to library logs
Date: Fri, 7 May 2021 12:50:18 +0300 [thread overview]
Message-ID: <20210507095022.1079364-1-tz.stoyanov@gmail.com> (raw)
Defined library log levels and add a new API to set the desired log level.
v2 changes:
- Add a parameter to tep_vprint() for errno printing, insted of using the log
level.
Tzvetomir Stoyanov (VMware) (4):
libtraceevent: Add log levels
libtraceevent: Add logs with severity info
libtraceevent: Rename tep_vwarning() to tep_vprint()
libtraceevent: Document new log functionality
Documentation/libtraceevent-log.txt | 90 +++++++++++++++++++++++++++++
Documentation/libtraceevent.txt | 3 +
src/event-parse.c | 14 ++---
src/event-parse.h | 12 ++++
src/event-plugin.c | 2 +-
src/event-utils.h | 12 ++--
src/parse-utils.c | 65 +++++++++++++--------
7 files changed, 158 insertions(+), 40 deletions(-)
create mode 100644 Documentation/libtraceevent-log.txt
--
2.31.1
next reply other threads:[~2021-05-07 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:50 Tzvetomir Stoyanov (VMware) [this message]
2021-05-07 9:50 ` [PATCH v2 1/4] libtraceevent: Add log levels Tzvetomir Stoyanov (VMware)
2021-05-07 9:50 ` [PATCH v2 2/4] libtraceevent: Add logs with severity info Tzvetomir Stoyanov (VMware)
2021-05-07 9:50 ` [PATCH v2 3/4] libtraceevent: Rename tep_vwarning() to tep_vprint() Tzvetomir Stoyanov (VMware)
2021-05-13 1:52 ` Steven Rostedt
2021-05-07 9:50 ` [PATCH v2 4/4] libtraceevent: Document new log functionality Tzvetomir Stoyanov (VMware)
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=20210507095022.1079364-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).