From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Andreas Ziegler <andreas.ziegler@fau.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing/uprobes: Fix output for multiple string arguments
Date: Thu, 17 Jan 2019 09:20:42 -0500 [thread overview]
Message-ID: <20190117092042.4f689462@vmware.local.home> (raw)
In-Reply-To: <20190117165807.64e95553ff397e7f73ba495b@kernel.org>
On Thu, 17 Jan 2019 16:58:07 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Ah, I got it.
> Hmm, in that case, I have to update my patch in the previous mail.
> Anyway,
>
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
So this patch is good to go? If so, I'll pull it in and start testing
it.
I'm currently traveling (as you probably received my OoO emails), but I
can still do a bit of work remotely.
-- Steve
next prev parent reply other threads:[~2019-01-17 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 12:38 uprobes: bug in comm/string output? Andreas Ziegler
2019-01-15 13:36 ` Andreas Ziegler
2019-01-16 9:41 ` [PATCH] tracing/uprobes: Fix output for multiple string arguments Andreas Ziegler
2019-01-16 13:40 ` Steven Rostedt
2019-01-16 14:13 ` Andreas Ziegler
2019-01-16 14:16 ` [PATCH v2] " Andreas Ziegler
2019-01-16 14:34 ` Steven Rostedt
2019-01-17 6:01 ` Masami Hiramatsu
2019-01-17 7:40 ` Andreas Ziegler
2019-01-17 7:58 ` Masami Hiramatsu
2019-01-17 14:20 ` Steven Rostedt [this message]
2019-01-17 14:29 ` Andreas Ziegler
2019-01-17 14:51 ` Steven Rostedt
2019-01-17 15:14 ` Andreas Ziegler
2019-01-17 15:35 ` Steven Rostedt
2019-01-16 10:00 ` uprobes: bug in comm/string output? Masami Hiramatsu
2019-01-16 10:16 ` Andreas Ziegler
2019-01-17 6:13 ` Masami Hiramatsu
2019-01-17 8:00 ` Masami Hiramatsu
2019-01-17 8:08 ` Andreas Ziegler
2019-01-17 9:47 ` Masami Hiramatsu
2019-01-17 13:44 ` Andreas Ziegler
2019-01-17 13:47 ` Greg Kroah-Hartman
2019-01-17 23:50 ` 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=20190117092042.4f689462@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=andreas.ziegler@fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.