From: Randy Dunlap <rdunlap@infradead.org>
To: Prasad Pandit <ppandit@redhat.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH] ftrace: fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry
Date: Fri, 22 Mar 2024 08:51:32 -0700 [thread overview]
Message-ID: <a9bddc1c-9652-400c-8f79-b745894604d9@infradead.org> (raw)
In-Reply-To: <20240322121801.1803948-1-ppandit@redhat.com>
On 3/22/24 05:18, Prasad Pandit wrote:
> From: Prasad Pandit <pjp@fedoraproject.org>
>
> Fix FTRACE_RECORD_RECURSION_SIZE entry, replace tab with
replace the tab between "default" and "128" with a space
> a space character. It helps Kconfig parsers to read file
> without error.
Parsers should accept either tab or space but this is a
reasonable change.
> Fixes: 773c16705058 ("ftrace: Add recording of functions that caused recursion")
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> kernel/trace/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index 61c541c36596..47345bf1d4a9 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -965,7 +965,7 @@ config FTRACE_RECORD_RECURSION
>
> config FTRACE_RECORD_RECURSION_SIZE
> int "Max number of recursed functions to record"
> - default 128
> + default 128
> depends on FTRACE_RECORD_RECURSION
> help
> This defines the limit of number of functions that can be
--
#Randy
prev parent reply other threads:[~2024-03-22 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 12:18 [PATCH] ftrace: fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry Prasad Pandit
2024-03-22 15:51 ` Randy Dunlap [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=a9bddc1c-9652-400c-8f79-b745894604d9@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--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 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).