From: Steven Rostedt <rostedt@goodmis.org>
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] apparent bogosity in unregister_ftrace_function_probe_func()
Date: Mon, 5 Feb 2018 21:48:32 -0500 [thread overview]
Message-ID: <20180205214832.62e83cbd@vmware.local.home> (raw)
In-Reply-To: <CAJwJo6aYu2qAHcrYD8mTn43+4Z5ikJ6qoM7SxPtG=NuVcYtauQ@mail.gmail.com>
On Tue, 6 Feb 2018 02:44:03 +0000
Dmitry Safonov <0x7f454c46@gmail.com> wrote:
> Yes, I've planned to do this..
> As it's merge-window now I thought doing this a week later.
> So, it's up to you - just let me know so we will not end doing the same fix :)
>
If you haven't done it already, I'll just do it. As it will not be much
more work with the tests I'll add for Al's updates.
Note, these are bug fixes (and will mark them for stable), and I plan to
send to Linus as soon as they are ready. They don't need to wait for the
merge window.
Thanks!
-- Steve
next prev parent reply other threads:[~2018-02-06 2:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 3:17 [RFC] apparent bogosity in unregister_ftrace_function_probe_func() Al Viro
2018-01-27 13:59 ` Dmitry Safonov
2018-01-27 17:07 ` Al Viro
2018-01-28 10:31 ` Steven Rostedt
2018-01-29 13:59 ` Masami Hiramatsu
2018-02-05 22:54 ` Steven Rostedt
2018-02-06 1:25 ` Dmitry Safonov
2018-02-06 2:26 ` Masami Hiramatsu
2018-02-06 2:40 ` Steven Rostedt
2018-02-06 2:44 ` Dmitry Safonov
2018-02-06 2:48 ` Steven Rostedt [this message]
2018-02-06 2:53 ` Dmitry Safonov
2018-01-29 13:49 ` Masami Hiramatsu
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=20180205214832.62e83cbd@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=0x7f454c46@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).