From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jeff Xie <xiehuan09@gmail.com>
Cc: rostedt@goodmis.org, mingo@redhat.com, mhiramat@kernel.org,
zanussi@kernel.org, linux-kernel@vger.kernel.org,
chensong_2000@189.cn, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v14 4/4] Documentation: trace/objtrace: Add documentation for objtrace
Date: Wed, 29 Jun 2022 16:28:18 +0700 [thread overview]
Message-ID: <YrwbMu9f7cGosYCT@debian.me> (raw)
In-Reply-To: <20220628145552.349839-5-xiehuan09@gmail.com>
On Tue, Jun 28, 2022 at 10:55:52PM +0800, Jeff Xie wrote:
> Add documentation explaining how to use objtrace trigger to get the value
> of the object.
>
Looks OK, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-29 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:55 [PATCH v14 0/4] trace: Introduce objtrace trigger to trace the kernel object 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 [this message]
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
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=YrwbMu9f7cGosYCT@debian.me \
--to=bagasdotme@gmail.com \
--cc=chensong_2000@189.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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 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.