From: Steven Rostedt <rostedt@goodmis.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: Ingo Molnar <mingo@redhat.com>, <kernel@axis.com>,
<tglx@linutronix.de>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Remove outdated comment in stack handling
Date: Mon, 27 Jul 2020 16:52:32 -0400 [thread overview]
Message-ID: <20200727165232.7495ed57@oasis.local.home> (raw)
In-Reply-To: <20200727092840.18659-1-vincent.whitchurch@axis.com>
On Mon, 27 Jul 2020 11:28:40 +0200
Vincent Whitchurch <vincent.whitchurch@axis.com> wrote:
> This comment describes the behaviour before commit 2a820bf74918
> ("tracing: Use percpu stack trace buffer more intelligently"). Since
> that commit, interrupts and NMIs do use the per-cpu stacks so the
> comment is no longer correct. Remove it.
>
Thanks, I'll queue this up for the next merge window.
-- Steve
> (Note that the FTRACE_STACK_SIZE mentioned in the comment has never
> existed, it probably should have said FTRACE_STACK_ENTRIES.)
>
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
prev parent reply other threads:[~2020-07-27 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:28 [PATCH] tracing: Remove outdated comment in stack handling Vincent Whitchurch
2020-07-27 20:52 ` Steven Rostedt [this message]
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=20200727165232.7495ed57@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vincent.whitchurch@axis.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