mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Xie <xiehuan09@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	mingo@redhat.com, Tom Zanussi <zanussi@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 0/4] trace: Introduce objtrace trigger to trace the kernel object
Date: Thu, 14 Apr 2022 12:52:45 -0400	[thread overview]
Message-ID: <20220414125245.400bdf4e@rorschach.local.home> (raw)
In-Reply-To: <CAEr6+EB61DZdga+74RXQufLvbXPZ-rJzTrhL+JC54N5-gQm8-Q@mail.gmail.com>

On Mon, 11 Apr 2022 23:47:23 +0800
Jeff Xie <xiehuan09@gmail.com> wrote:

> Just don't want you to forget this patch series ;-)

I won't. I've just been super busy (on my way back home from Denver).
I'll try to get some time tomorrow to review them.

Thanks for being patient with me.

-- Steve

      reply	other threads:[~2022-04-14 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  3:56 Jeff Xie
2022-02-04  3:56 ` [PATCH v9 1/4] trace: Add trace any " Jeff Xie
2022-04-19  2:14   ` Steven Rostedt
2022-04-19  2:26     ` Steven Rostedt
2022-04-19 16:26     ` Jeff Xie
2022-04-27 15:50   ` Jeff Xie
2022-05-02 17:42     ` Tom Zanussi
2022-05-04  7:42       ` Jeff Xie
2022-02-04  3:56 ` [PATCH v9 2/4] trace/objtrace: get the value of the object Jeff Xie
2022-02-04  3:56 ` [PATCH v9 3/4] trace/objtrace: Add testcases for objtrace Jeff Xie
2022-02-04  3:56 ` [PATCH v9 4/4] trace/objtrace: Add documentation " Jeff Xie
2022-02-08 14:08 ` [PATCH v9 0/4] trace: Introduce objtrace trigger to trace the kernel object Masami Hiramatsu
2022-02-08 15:48   ` Steven Rostedt
2022-02-26 16:01     ` Jeff Xie
2022-02-28 16:08       ` Steven Rostedt
2022-03-22 17:20         ` Jeff Xie
2022-04-11 15:47           ` Jeff Xie
2022-04-14 16:52             ` Steven Rostedt [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=20220414125245.400bdf4e@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=xiehuan09@gmail.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
all inboxes | Powered by JetHome®