From: Beau Belgrave <beaub@linux.microsoft.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: rostedt@goodmis.org, mhiramat@kernel.org,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 10/10] user_events: Add documentation file
Date: Thu, 4 Nov 2021 14:08:09 -0700 [thread overview]
Message-ID: <20211104210809.GA2486@kbox> (raw)
In-Reply-To: <8735obrbao.fsf@meer.lwn.net>
On Thu, Nov 04, 2021 at 01:05:51PM -0600, Jonathan Corbet wrote:
> Beau Belgrave <beaub@linux.microsoft.com> writes:
>
> > Add a documentation file about user_events with example code, etc.
> > explaining how it may be used.
>
> Yay documentation! Some nits for a slow moment...
>
> > Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> > ---
> > Documentation/trace/user_events.rst | 298 ++++++++++++++++++++++++++++
> > 1 file changed, 298 insertions(+)
> > create mode 100644 Documentation/trace/user_events.rst
>
> Actually, this isn't really a nit. When you add a new RST file, you
> need to add it to the index.rst file too so that it gets pulled into the
> docs build. Otherwise you'll get the warning you doubtless saw when you
> tried building the docs after adding this file...:)
>
Thanks for the review, I'll fix these things up!
> > +Example Code
> > +------------
>
> Examples are great, but they are best placed under samples/ (or tools/
> if they do something useful) where readers can build and run them.
>
Ok, sounds good. Is it fine to include user mode samples in there? I
quickly checked and most appear to be modules. Maybe there is a better
place for user mode examples?
Thanks,
-Beau
next prev parent reply other threads:[~2021-11-04 21:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 17:04 [PATCH v4 00/10] user_events: Enable user processes to create and write to trace events Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 01/10] user_events: Add UABI header for user access to user_events Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 02/10] user_events: Add minimal support for trace_event into ftrace Beau Belgrave
2021-11-04 21:34 ` kernel test robot
2021-11-08 2:32 ` Masami Hiramatsu
2021-11-08 16:59 ` Beau Belgrave
2021-11-07 14:31 ` Masami Hiramatsu
2021-11-08 17:13 ` Beau Belgrave
2021-11-08 18:16 ` Steven Rostedt
2021-11-08 20:25 ` Beau Belgrave
2021-11-08 21:00 ` Steven Rostedt
2021-11-08 22:09 ` Beau Belgrave
2021-11-08 22:30 ` Steven Rostedt
2021-11-08 22:59 ` Beau Belgrave
2021-11-09 4:58 ` Masami Hiramatsu
2021-11-09 2:56 ` Masami Hiramatsu
2021-11-09 19:08 ` Beau Belgrave
2021-11-09 19:25 ` Steven Rostedt
2021-11-09 20:14 ` Beau Belgrave
2021-11-09 20:45 ` Steven Rostedt
2021-11-09 21:27 ` Beau Belgrave
2021-11-09 21:39 ` Steven Rostedt
2021-11-10 13:56 ` Masami Hiramatsu
2021-11-11 17:33 ` Beau Belgrave
2021-11-12 13:40 ` Masami Hiramatsu
2021-11-07 18:18 ` Steven Rostedt
2021-11-08 19:56 ` Beau Belgrave
2021-11-08 20:53 ` Steven Rostedt
2021-11-08 21:15 ` Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 03/10] user_events: Add print_fmt generation support for basic types Beau Belgrave
2021-11-08 22:03 ` Steven Rostedt
2021-11-04 17:04 ` [PATCH v4 04/10] user_events: Handle matching arguments from dyn_events Beau Belgrave
2021-11-08 22:05 ` Steven Rostedt
2021-11-04 17:04 ` [PATCH v4 05/10] user_events: Add basic perf and eBPF support Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 06/10] user_events: Add self-test for ftrace integration Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 07/10] user_events: Add self-test for dynamic_events integration Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 08/10] user_events: Add self-test for perf_event integration Beau Belgrave
2021-11-04 17:04 ` [PATCH v4 09/10] user_events: Optimize writing events by only copying data once Beau Belgrave
2021-11-08 22:45 ` Steven Rostedt
2021-11-08 23:00 ` Beau Belgrave
2021-11-08 23:04 ` Steven Rostedt
2021-11-08 23:17 ` Beau Belgrave
2021-11-08 23:20 ` Steven Rostedt
2021-11-04 17:04 ` [PATCH v4 10/10] user_events: Add documentation file Beau Belgrave
2021-11-04 19:05 ` Jonathan Corbet
2021-11-04 21:08 ` Beau Belgrave [this message]
2021-11-04 21:18 ` Jonathan Corbet
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=20211104210809.GA2486@kbox \
--to=beaub@linux.microsoft.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).