From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] trace: Relocate event helper files
Date: Mon, 14 Nov 2022 10:18:54 -0500 [thread overview]
Message-ID: <20221114101854.35bd75c4@gandalf.local.home> (raw)
In-Reply-To: <C11D5606-4432-4FBC-8754-CA49832D172F@oracle.com>
On Mon, 14 Nov 2022 15:13:56 +0000
Chuck Lever III <chuck.lever@oracle.com> wrote:
> > Probably needs to be updated in the Documentation/trace/events.rst?
>
> That file seems to be a user's guide, not a programmer's guide.
Good point. Perhaps its time to make a events-howto.rst document, that can
use the input from the samples/trace_events/ directory.
-- Steve
prev parent reply other threads:[~2022-11-14 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 14:36 [PATCH v1] trace: Relocate event helper files Chuck Lever
2022-11-14 15:02 ` Steven Rostedt
2022-11-14 15:03 ` Steven Rostedt
2022-11-14 15:13 ` Chuck Lever III
2022-11-14 15:18 ` 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=20221114101854.35bd75c4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.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