From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, Alex Shi <alex.shi@linaro.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Jon Medhurst <tixy@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH 0/2] selftests: ftrace: Fix multiple-kprobe testcase
Date: Mon, 15 Jan 2018 13:05:57 -0500 [thread overview]
Message-ID: <20180115130557.34aaac4f@gandalf.local.home> (raw)
In-Reply-To: <151593777761.23875.10360397710751679883.stgit@devbox>
Shuah,
Want to take these in your tree? You can add:
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
On Sun, 14 Jan 2018 22:49:37 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hi,
>
> These patches are fixing a bug and improve testcase to
> ensure adding 256 kprobe events for test.
>
> I've just updated to the latest kselftest/master branch.
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (2):
> [BUGFIX] selftest: ftrace: Fix to pick text symbols for kprobes
> selftest: ftrace: Fix to add 256 kprobe events correctly
>
>
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 21 +++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> --
> Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-01-15 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 13:49 Masami Hiramatsu
2018-01-14 13:50 ` [RESEND PATCH 1/2] [BUGFIX] selftest: ftrace: Fix to pick text symbols for kprobes Masami Hiramatsu
2018-01-14 13:50 ` [RESEND PATCH 2/2] selftest: ftrace: Fix to add 256 kprobe events correctly Masami Hiramatsu
2018-01-15 18:05 ` Steven Rostedt [this message]
2018-01-16 16:33 ` [RESEND PATCH 0/2] selftests: ftrace: Fix multiple-kprobe testcase Shuah Khan
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=20180115130557.34aaac4f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alex.shi@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=tixy@linaro.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
all inboxes | Powered by JetHome®