From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Xie <xiehuan09@gmail.com>
Cc: mhiramat@kernel.org, mingo@redhat.com, zanussi@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/4] trace: Add trace any kernel object
Date: Mon, 18 Apr 2022 22:26:25 -0400 [thread overview]
Message-ID: <20220418222625.3e0c5ff8@rorschach.local.home> (raw)
In-Reply-To: <20220418214400.2ab7f932@rorschach.local.home>
On Mon, 18 Apr 2022 22:14:31 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> We need to consolidate the code a bit, and add helper functions to
> share between them, instead of just cut and pasting and tweaking.
> That's a maintenance nightmare.
And I forgot that Tom started to do this and I haven't applied his
patches yet. I'll start applying them now.
https://lore.kernel.org/all/cover.1644010575.git.zanussi@kernel.org/
So when that is done, you can look at rebasing on top of it. Which will
hopefully make the code a bit simpler.
-- Steve
next prev parent reply other threads:[~2022-04-19 2:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 3:56 [PATCH v9 0/4] trace: Introduce objtrace trigger to trace the " 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 [this message]
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
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=20220418222625.3e0c5ff8@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®