From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <zanussi@kernel.org>
Cc: Axel Rasmussen <axelrasmussen@google.com>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <walken@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Laurent Dufour <ldufour@linux.ibm.com>,
Jann Horn <jannh@google.com>,
Chinwen Chang <chinwen.chang@mediatek.com>,
Yafang Shao <laoar.shao@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 1/2] tracing: support "bool" type in synthetic trace events
Date: Mon, 12 Oct 2020 10:46:14 -0400 [thread overview]
Message-ID: <20201012104614.25ea97bc@gandalf.local.home> (raw)
In-Reply-To: <43b10ad23a80ee5ae9f10b6d47d7944b6b14a25d.camel@kernel.org>
On Mon, 12 Oct 2020 09:26:13 -0500
Tom Zanussi <zanussi@kernel.org> wrote:
> Hi Steve,
>
> Looks ok to me.
>
> Acked-by: Tom Zanussi <zanussi@kernel.org>
Great!
I'll pull this patch into my tree. It doesn't look like patch 2/2 is
dependent on this and these two can go through different trees.
Is everyone OK if I take this patch through my tree?
-- Steve
next prev parent reply other threads:[~2020-10-12 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 22:05 [PATCH v3 0/2] Add tracepoints around mmap_lock acquisition Axel Rasmussen
2020-10-09 22:05 ` [PATCH v3 1/2] tracing: support "bool" type in synthetic trace events Axel Rasmussen
2020-10-12 14:15 ` Steven Rostedt
2020-10-12 14:26 ` Tom Zanussi
2020-10-12 14:46 ` Steven Rostedt [this message]
2020-10-12 16:23 ` Axel Rasmussen
2020-10-13 19:41 ` David Rientjes
2020-10-09 22:05 ` [PATCH v3 2/2] mmap_lock: add tracepoints around lock acquisition Axel Rasmussen
2020-10-09 22:35 ` Michel Lespinasse
2020-10-10 5:31 ` Yafang Shao
2020-10-13 19:42 ` David Rientjes
2020-10-20 14:50 ` Vlastimil Babka
2020-10-20 18:17 ` Axel Rasmussen
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=20201012104614.25ea97bc@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chinwen.chang@mediatek.com \
--cc=daniel.m.jordan@oracle.com \
--cc=jannh@google.com \
--cc=laoar.shao@gmail.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=vbabka@suse.cz \
--cc=walken@google.com \
--cc=zanussi@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;
as well as URLs for NNTP newsgroup(s).