From: Ross Zwisler <zwisler@google.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Ross Zwisler <zwisler@chromium.org>,
linux-kernel@vger.kernel.org, "Tobin C. Harding" <me@tobin.cc>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Wang <jasowang@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, Tycho Andersen <tycho@tycho.pizza>,
kvm@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux-foundation.org,
linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 0/6] use canonical ftrace path whenever possible
Date: Wed, 22 Mar 2023 10:52:33 -0600 [thread overview]
Message-ID: <20230322165233.GA2583234@google.com> (raw)
In-Reply-To: <20230321223139-mutt-send-email-mst@kernel.org>
On Tue, Mar 21, 2023 at 10:32:46PM -0400, Michael S. Tsirkin wrote:
> On Wed, Feb 15, 2023 at 03:33:44PM -0700, Ross Zwisler wrote:
> > Changes in v2:
> > * Dropped patches which were pulled into maintainer trees.
> > * Split BPF patches out into another series targeting bpf-next.
> > * trace-agent now falls back to debugfs if tracefs isn't present.
> > * Added Acked-by from mst@redhat.com to series.
> > * Added a typo fixup for the virtio-trace README.
> >
> > Steven, assuming there are no objections, would you feel comfortable
> > taking this series through your tree?
>
> for merging up to patch 5 through another tree:
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> I'll merge patch 6, no problem.
Hey Michael, would you also mind merging patch 5, the other virtio patch?
[PATCH v2 5/6] tools/virtio: use canonical ftrace path
https://lore.kernel.org/all/20230215223350.2658616-6-zwisler@google.com/
I don't think Steven took this one through his tree. Thanks!
prev parent reply other threads:[~2023-03-22 16:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 22:33 [PATCH v2 0/6] use canonical ftrace path whenever possible Ross Zwisler
2023-02-15 22:33 ` [PATCH v2 1/6] tracing: always use canonical ftrace path Ross Zwisler
2023-02-16 15:13 ` Masami Hiramatsu
2023-02-17 15:34 ` Mukesh Ojha
2023-02-15 22:33 ` [PATCH v2 2/6] selftests: " Ross Zwisler
2023-02-16 20:58 ` Steven Rostedt
2023-02-17 15:40 ` Mukesh Ojha
2023-02-15 22:33 ` [PATCH v2 3/6] leaking_addresses: also skip " Ross Zwisler
2023-02-15 22:33 ` [PATCH v2 4/6] tools/kvm_stat: use " Ross Zwisler
2023-02-16 21:08 ` Steven Rostedt
2023-02-17 11:32 ` Paolo Bonzini
2023-02-17 15:41 ` Mukesh Ojha
2023-02-15 22:33 ` [PATCH v2 5/6] tools/virtio: " Ross Zwisler
2023-02-17 15:46 ` Mukesh Ojha
2023-06-02 11:15 ` Michael S. Tsirkin
2023-06-02 11:15 ` Michael S. Tsirkin
2023-02-15 22:33 ` [PATCH v2 6/6] tools/virtio: fix typo in README instructions Ross Zwisler
2023-03-10 8:29 ` [PATCH v2 0/6] use canonical ftrace path whenever possible Michael S. Tsirkin
2023-03-10 8:29 ` Michael S. Tsirkin
2023-03-10 19:06 ` Ross Zwisler
2023-03-10 19:37 ` Steven Rostedt
2023-03-10 19:37 ` Steven Rostedt
2023-03-22 2:32 ` Michael S. Tsirkin
2023-03-22 2:32 ` Michael S. Tsirkin
2023-03-22 16:52 ` Ross Zwisler [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=20230322165233.GA2583234@google.com \
--to=zwisler@google.com \
--cc=akpm@linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=mhiramat@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tycho@tycho.pizza \
--cc=virtualization@lists.linux-foundation.org \
--cc=zwisler@chromium.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 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.