From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH] trace-cmd: Suppress trace library warnings
Date: Fri, 16 Apr 2021 10:01:18 -0400 [thread overview]
Message-ID: <20210416100118.585d3865@gandalf.local.home> (raw)
In-Reply-To: <20210416095908.258d4c96@gandalf.local.home>
On Fri, 16 Apr 2021 09:59:08 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> As for pr_stat(), I think we should rename it to tep_info() and tep_vinfo()
> that acts just like tep_warning(), except it is for informational output
> (stdout instead of stderr). This is similar to what the kernel has.
>
> Since tep_vwarning() takes a name, so can tep_vinfo(), and I was thinking
> that we should expose this string to the application.
>
Oh, and we could add a tep_critical() and tep_vcritical() which means that
the error is something really bad happened, (like failed to allocate).
-- Steve
next prev parent reply other threads:[~2021-04-16 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 8:03 [PATCH] trace-cmd: Suppress trace library warnings Tzvetomir Stoyanov (VMware)
2021-04-15 13:34 ` Steven Rostedt
2021-04-16 10:14 ` Tzvetomir Stoyanov
2021-04-16 13:59 ` Steven Rostedt
2021-04-16 14:01 ` Steven Rostedt [this message]
2021-04-22 20:25 ` Steven Rostedt
2021-04-28 7:51 ` Tzvetomir Stoyanov
2021-04-15 8:15 [PATCH 0/3] Fix overflow when applying tsc2nsec calculations Tzvetomir Stoyanov (VMware)
2021-04-15 8:15 ` [PATCH] trace-cmd: Suppress trace library warnings 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=20210416100118.585d3865@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.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).