From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/3] Add API to set severity to tracefs library logs
Date: Fri, 7 May 2021 12:51:51 +0300 [thread overview]
Message-ID: <20210507095154.1080202-1-tz.stoyanov@gmail.com> (raw)
A new API to set the desired log level of the library.
These changes depend on "[PATCH 0/4] Add severity to library logs"
https://lore.kernel.org/linux-trace-devel/20210507095022.1079364-1-tz.stoyanov@gmail.com/
v2 changes:
- Add a parameter to tep_vprint() for errno printing, insted of using the log
level.
- Added a patch to remove unneeded tep_vwarning() implementation from the unit
tests.
Tzvetomir Stoyanov (VMware) (3):
libtracefs: Add API to set the log level
libtracefs: Document new log functionality
libtracefs: Remove dummy tep_vwarning() from unit tests
Documentation/libtracefs-log.txt | 76 ++++++++++++++++++++++++++++++++
Documentation/libtracefs.txt | 2 +
include/tracefs.h | 4 ++
src/tracefs-utils.c | 18 +++++++-
utest/trace-utest.c | 5 ---
5 files changed, 99 insertions(+), 6 deletions(-)
create mode 100644 Documentation/libtracefs-log.txt
--
2.31.1
next reply other threads:[~2021-05-07 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:51 Tzvetomir Stoyanov (VMware) [this message]
2021-05-07 9:51 ` [PATCH v2 1/3] libtracefs: Add API to set the log level Tzvetomir Stoyanov (VMware)
2021-05-07 9:51 ` [PATCH v2 2/3] libtracefs: Document new log functionality Tzvetomir Stoyanov (VMware)
2021-05-07 9:51 ` [PATCH v2 3/3] libtracefs: Remove dummy tep_vwarning() from unit tests 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=20210507095154.1080202-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 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.