From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Akanksha J N <akanksha@linux.ibm.com>,
linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah@kernel.org, naveen.n.rao@linux.ibm.com
Subject: Re: [PATCH v3 2/2] selftests/ftrace: Add new test case which checks for optimized probes
Date: Thu, 18 May 2023 13:29:41 +0900 [thread overview]
Message-ID: <20230518132941.0d2c3a4dde48063514e001d4@kernel.org> (raw)
In-Reply-To: <08abb08f-68d9-54d0-cb7a-ba56a73a9856@linuxfoundation.org>
On Wed, 17 May 2023 10:26:43 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 5/12/23 16:15, Steven Rostedt wrote:
> > On Mon, 8 May 2023 11:36:28 -0600
> > Shuah Khan <skhan@linuxfoundation.org> wrote:
> >
> >>> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >>>
> >>
> >> Would you like this patch to go through kselftest tree?
> >
> > Shuah, you can take it through your kselftest tree.
> >
> > Thanks!
> >
> > Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> >
>
> Applied to linux-kselftest next for 6.5-rc1
Thank you Shuah!
>
> thanks,
> -- Shuah
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-05-18 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 16:38 [PATCH v3 0/2] selftests/ftrace: Add tests for kprobes and optimized probes Akanksha J N
2023-04-28 16:38 ` [PATCH v3 1/2] selftests/ftrace: Add new test case which adds multiple consecutive probes in a function Akanksha J N
2023-04-28 16:38 ` [PATCH v3 2/2] selftests/ftrace: Add new test case which checks for optimized probes Akanksha J N
2023-04-30 1:52 ` Masami Hiramatsu
2023-05-08 17:36 ` Shuah Khan
2023-05-12 22:15 ` Steven Rostedt
2023-05-17 16:26 ` Shuah Khan
2023-05-18 4:29 ` Masami Hiramatsu [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=20230518132941.0d2c3a4dde48063514e001d4@kernel.org \
--to=mhiramat@kernel.org \
--cc=akanksha@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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).