From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Andrew Morton <akpm@linux-foundation.org>,
Changbin Du <changbin.du@gmail.com>, Jann Horn <jannh@google.com>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Nadav Amit <namit@vmware.com>,
Joel Fernandes <joel@joelfernandes.org>,
yhs@fb.com
Subject: Re: [PATCH -tip v9 0/6] tracing/probes: uaccess: Add support user-space access
Date: Mon, 20 May 2019 11:26:05 -0400 [thread overview]
Message-ID: <20190520112605.421bda88@gandalf.local.home> (raw)
In-Reply-To: <20190515055534.GA39270@gmail.com>
On Wed, 15 May 2019 07:55:34 +0200
Ingo Molnar <mingo@kernel.org> wrote:
> * Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Hi,
> >
> > Here is the v9 series of probe-event to support user-space access.
> > Previous version is here.
> >
> > https://lkml.kernel.org/r/155741476971.28419.15837024173365724167.stgit@devnote2
> >
> > In this version, I fixed more typos/style issues.
> >
> > Changes in v9:
> > [3/6]
> > - Fix other style & coding issues (Thanks Ingo!)
> > - Update fetch_store_string() for style consistency.
> > [4/6]
> > - Remove an unneeded line break.
> > - Move || and && in if-condition at the end of line.
>
> LGTM:
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
>
Hi Ingo,
Do you want me to take this through my tree, or do you want to take it
through yours?
Thanks,
-- Steve
next prev parent reply other threads:[~2019-05-20 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 5:37 [PATCH -tip v9 0/6] tracing/probes: uaccess: Add support user-space access Masami Hiramatsu
2019-05-15 5:38 ` [PATCH -tip v9 1/6] x86/uaccess: Allow access_ok() in irq context if pagefault_disabled Masami Hiramatsu
2019-05-15 5:38 ` [PATCH -tip v9 2/6] uaccess: Add non-pagefault user-space read functions Masami Hiramatsu
2019-05-15 5:38 ` [PATCH -tip v9 3/6] tracing/probe: Add ustring type for user-space string Masami Hiramatsu
2019-05-15 5:38 ` [PATCH -tip v9 4/6] tracing/probe: Support user-space dereference Masami Hiramatsu
2019-05-15 5:38 ` [PATCH -tip v9 5/6] selftests/ftrace: Add user-memory access syntax testcase Masami Hiramatsu
2019-05-15 5:39 ` [PATCH -tip v9 6/6] perf-probe: Add user memory access attribute support Masami Hiramatsu
2019-05-15 5:55 ` [PATCH -tip v9 0/6] tracing/probes: uaccess: Add support user-space access Ingo Molnar
2019-05-15 8:49 ` Masami Hiramatsu
2019-05-20 15:26 ` Steven Rostedt [this message]
2019-05-21 8:28 ` Ingo Molnar
2019-05-21 12:57 ` Steven Rostedt
2019-05-21 15:57 ` 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=20190520112605.421bda88@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=changbin.du@gmail.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yhs@fb.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 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).