From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Shuah Khan <shuah@kernel.org>, Xuefeng Li <lixuefeng@loongson.cn>,
linux-mips@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Modify some code about kprobe
Date: Thu, 12 May 2022 18:10:54 +0200 [thread overview]
Message-ID: <20220512161054.GE14475@alpha.franken.de> (raw)
In-Reply-To: <1651834923-31573-1-git-send-email-yangtiezhu@loongson.cn>
On Fri, May 06, 2022 at 07:02:01PM +0800, Tiezhu Yang wrote:
> v3: no need to change post_kprobe_handler() in patch #2 now,
> sorry for the carelessness.
>
> v2:
> -- only replace __kprobes with NOKPROBE_SYMBOL() in patch #2
> -- update the commit messages
>
> Tiezhu Yang (2):
> selftests/ftrace: Save kprobe_events to test log
> MIPS: Use NOKPROBE_SYMBOL() instead of __kprobes annotation
>
> arch/mips/kernel/kprobes.c | 36 ++++++++++++++--------
> arch/mips/mm/fault.c | 6 ++--
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 2 ++
> 3 files changed, 30 insertions(+), 14 deletions(-)
>
> --
> 2.1.0
seires applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-05-12 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 11:02 Tiezhu Yang
2022-05-06 11:02 ` [PATCH v3 1/2] selftests/ftrace: Save kprobe_events to test log Tiezhu Yang
2022-05-06 11:02 ` [PATCH v3 2/2] MIPS: Use NOKPROBE_SYMBOL() instead of __kprobes annotation Tiezhu Yang
2022-05-07 3:47 ` Masami Hiramatsu
2022-05-12 16:10 ` Thomas Bogendoerfer [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=20220512161054.GE14475@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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®