From: Shuah Khan <skhan@linuxfoundation.org>
To: Vincenzo Mezzela <vincenzo.mezzela@gmail.com>,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, shuah@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftest: ftrace: fix minor typo in log
Date: Tue, 20 Feb 2024 16:41:01 -0700 [thread overview]
Message-ID: <7459e07b-80fb-4eae-9414-3dee68cfd173@linuxfoundation.org> (raw)
In-Reply-To: <20240211111818.610211-1-vincenzo.mezzela@gmail.com>
On 2/11/24 04:18, Vincenzo Mezzela wrote:
> Resolves a spelling error in the test log, preventing potential
> confusion.
>
> Signed-off-by: Vincenzo Mezzela <vincenzo.mezzela@gmail.com>
> ---
>
> It is submitted as part of my application to the "Linux Kernel
> Bug Fixing Spring Unpaid 2024" mentorship program of the Linux
> Foundation.
>
> .../testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> index 4562e13cb26b..717898894ef7 100644
> --- a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> +++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> @@ -40,7 +40,7 @@ grep "id: \(unknown_\|sys_\)" events/raw_syscalls/sys_exit/hist > /dev/null || \
>
> reset_trigger
>
> -echo "Test histgram with log2 modifier"
> +echo "Test histogram with log2 modifier"
>
> echo 'hist:keys=bytes_req.log2' > events/kmem/kmalloc/trigger
> for i in `seq 1 10` ; do ( echo "forked" > /dev/null); done
Steve,
I picked this up fpr next for Linux 6.9-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2024-02-20 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 11:18 Vincenzo Mezzela
2024-02-20 23:41 ` Shuah Khan [this message]
2024-02-21 0:02 ` 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=7459e07b-80fb-4eae-9414-3dee68cfd173@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=vincenzo.mezzela@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
all inboxes | Powered by JetHome®