From: Masami Hiramatsu <mhiramat@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jessica Yu <jeyu@kernel.org>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] kprobes: improve error handling when arming/disarming kprobes
Date: Wed, 14 Feb 2018 09:45:51 +0900 [thread overview]
Message-ID: <20180214094551.7ef89492ae84806a0178c8ec@kernel.org> (raw)
In-Reply-To: <20180213172119.yurad3j3wyhapt74@gmail.com>
On Tue, 13 Feb 2018 18:21:19 +0100
Ingo Molnar <mingo@kernel.org> wrote:
>
> * Joe Lawrence <joe.lawrence@redhat.com> wrote:
>
> > Was this patch ever picked up in the tip tree? (Maybe I'm not looking
> > in the right branch?)
>
> Sorry, had a bit of a backlog: I picked up the two fixes/improvements now, and
> they will show up in tip:perf/urgent once they go through some local testing.
>
> Thanks!
Thanks Ingo!
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-02-14 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 23:51 [PATCH v5 0/2] kprobes: improve error handling when arming/disarming kprobes Jessica Yu
2018-01-09 23:51 ` [PATCH v5 1/2] kprobes: propagate error from arm_kprobe_ftrace() Jessica Yu
2018-02-13 18:46 ` [tip:perf/urgent] kprobes: Propagate " tip-bot for Jessica Yu
2018-02-16 9:46 ` tip-bot for Jessica Yu
2018-01-09 23:51 ` [PATCH v5 2/2] kprobes: propagate error from disarm_kprobe_ftrace() Jessica Yu
2018-02-13 18:46 ` [tip:perf/urgent] kprobes: Propagate " tip-bot for Jessica Yu
2018-02-16 9:47 ` tip-bot for Jessica Yu
2018-01-11 12:07 ` [PATCH v5 0/2] kprobes: improve error handling when arming/disarming kprobes Masami Hiramatsu
2018-01-19 7:06 ` Masami Hiramatsu
2018-02-13 17:05 ` Joe Lawrence
2018-02-13 17:21 ` Ingo Molnar
2018-02-14 0:45 ` 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=20180214094551.7ef89492ae84806a0178c8ec@kernel.org \
--to=mhiramat@kernel.org \
--cc=jeyu@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mingo@kernel.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