From: Steven Rostedt <rostedt@goodmis.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
kgdb-bugreport@lists.sourceforge.net,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] tracing: Add trace_total_entries() / trace_total_entries_cpu()
Date: Mon, 18 Mar 2019 17:18:46 -0400 [thread overview]
Message-ID: <20190318171846.2b4fd8dd@gandalf.local.home> (raw)
In-Reply-To: <20190318204741.116550-2-dianders@chromium.org>
On Mon, 18 Mar 2019 13:47:40 -0700
Douglas Anderson <dianders@chromium.org> wrote:
> These two new exported functions will be used in a future patch by
> kdb_ftdump() to quickly skip all but the last few trace entries.
>
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Actually, I guess only this email needs the ack from Daniel.
-- Steve
next prev parent reply other threads:[~2019-03-18 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 20:47 [PATCH v5 1/3] tracing: kdb: The skip_lines parameter should have been skip_entries Douglas Anderson
2019-03-18 20:47 ` [PATCH v5 2/3] tracing: Add trace_total_entries() / trace_total_entries_cpu() Douglas Anderson
2019-03-18 21:18 ` Steven Rostedt [this message]
2019-03-19 11:30 ` Daniel Thompson
2019-03-19 11:25 ` Daniel Thompson
2019-03-19 14:45 ` Doug Anderson
2019-03-19 14:55 ` Steven Rostedt
2019-03-19 15:56 ` Daniel Thompson
2019-03-18 20:47 ` [PATCH v5 3/3] tracing: kdb: Allow ftdump to skip all but the last few entries Douglas Anderson
2019-03-18 21:18 ` [PATCH v5 1/3] tracing: kdb: The skip_lines parameter should have been skip_entries Steven Rostedt
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=20190318171846.2b4fd8dd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=briannorris@chromium.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®