From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Xie <xiehuan09@gmail.com>
Cc: mingo@redhat.com, Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>,
linux-kernel@vger.kernel.org, Song Chen <chensong_2000@189.cn>
Subject: Re: [PATCH v14 0/4] trace: Introduce objtrace trigger to trace the kernel object
Date: Thu, 18 Aug 2022 11:26:44 -0400 [thread overview]
Message-ID: <20220818112644.40da65bf@gandalf.local.home> (raw)
In-Reply-To: <CAEr6+ECutZuYZNYzv-oD7Ss5nfg8eFAdwDG75E5NhM3UtkmH1A@mail.gmail.com>
On Thu, 18 Aug 2022 23:05:19 +0800
Jeff Xie <xiehuan09@gmail.com> wrote:
> Hi steve,
>
> I would like to ask whether this patch set may be merged into v6.1 ;-)
> The kernel development is indeed very different from what I originally imagined.
> I originally thought that objtrace would soon enter the kernel
> community, but I know
> it may take one to two years, or longer or discarded, I have slowly
> come to accept this reality ;-)
As, sorry for the late reviews (trying to get through all the other patches
too). I'll see if I can look at it this week.
-- Steve
next prev parent reply other threads:[~2022-08-18 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:55 Jeff Xie
2022-06-28 14:55 ` [PATCH v14 1/4] trace: Add trace any " Jeff Xie
2022-06-28 14:55 ` [PATCH v14 2/4] trace/objtrace: Get the value of the object Jeff Xie
2022-06-28 14:55 ` [PATCH v14 3/4] selftests/ftrace: Add testcases for objtrace Jeff Xie
2022-06-28 14:55 ` [PATCH v14 4/4] Documentation: trace/objtrace: Add documentation " Jeff Xie
2022-06-29 9:28 ` Bagas Sanjaya
2022-08-18 15:53 ` Joel Fernandes
2022-08-18 16:37 ` Jeff Xie
2022-08-18 17:05 ` Joel Fernandes
2022-08-18 17:34 ` Jeff Xie
2022-08-18 18:55 ` Joel Fernandes
2022-07-05 15:30 ` [PATCH v14 0/4] trace: Introduce objtrace trigger to trace the kernel object Jeff Xie
2022-07-05 17:49 ` Steven Rostedt
2022-08-18 15:05 ` Jeff Xie
2022-08-18 15:26 ` Steven Rostedt [this message]
2022-08-18 15:49 ` Jeff Xie
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=20220818112644.40da65bf@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chensong_2000@189.cn \
--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®