From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
tglx@linutronix.de, vedang.patel@intel.com,
bigeasy@linutronix.de, joel.opensrc@gmail.com, joelaf@google.com,
mathieu.desnoyers@efficios.com, baohong.liu@intel.com,
rajvi.jingar@intel.com, julia@ni.com, fengguang.wu@intel.com,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
kernel-team@lge.com
Subject: Re: [PATCH 2/6] tracing: Add trace event error log
Date: Thu, 19 Apr 2018 10:36:45 -0400 [thread overview]
Message-ID: <20180419103645.5e244e22@gandalf.local.home> (raw)
In-Reply-To: <20180419004033.GA13370@sejong>
On Thu, 19 Apr 2018 09:40:33 +0900
Namhyung Kim <namhyung@kernel.org> wrote:
> > I totally agree. I just want to make sure that whatever we come up with
> > will be well thought out. Perhaps we can wait till November to talk
> > about it.
>
> I'm not sure I can go to LPC this year, but definitely interested in
> improving error logging for tracing.
Feel free to send any ideas to us that you would like for us to add to
this discussion.
-- Steve
next prev parent reply other threads:[~2018-04-19 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 15:13 [PATCH 0/6] tracing: trace event error_log and inter-event bugfixes Tom Zanussi
2018-04-12 15:13 ` [PATCH 1/6] tracing: Restore proper field flag printing when displaying triggers Tom Zanussi
2018-04-12 15:13 ` [PATCH 2/6] tracing: Add trace event error log Tom Zanussi
2018-04-12 22:20 ` Steven Rostedt
2018-04-12 23:52 ` Tom Zanussi
2018-04-13 13:45 ` Steven Rostedt
2018-04-13 14:24 ` Tom Zanussi
2018-04-13 14:44 ` Steven Rostedt
2018-04-18 9:34 ` Masami Hiramatsu
2018-04-18 13:49 ` Steven Rostedt
2018-04-19 0:40 ` Namhyung Kim
2018-04-19 14:36 ` Steven Rostedt [this message]
2018-04-14 6:31 ` Masami Hiramatsu
2018-04-12 15:13 ` [PATCH 3/6] tracing: Save the last hist command's associated event name Tom Zanussi
2018-04-12 15:13 ` [PATCH 4/6] tracing: Use trace event error_log with hist triggers Tom Zanussi
2018-04-12 15:13 ` [PATCH 5/6] tracing: Add field parsing trace event errors for " Tom Zanussi
2018-04-12 15:13 ` [PATCH 6/6] selftests: ftrace: Fix extended error support testcase Tom Zanussi
2019-01-16 3:31 ` [PATCH 0/6] tracing: trace event error_log and inter-event bugfixes Steven Rostedt
2019-01-16 15:42 ` Tom Zanussi
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=20180419103645.5e244e22@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=baohong.liu@intel.com \
--cc=bigeasy@linutronix.de \
--cc=fengguang.wu@intel.com \
--cc=joel.opensrc@gmail.com \
--cc=joelaf@google.com \
--cc=julia@ni.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rajvi.jingar@intel.com \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=vedang.patel@intel.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).