From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] trace: Relocate event helper files
Date: Mon, 14 Nov 2022 10:02:14 -0500 [thread overview]
Message-ID: <20221114100214.55848d8c@gandalf.local.home> (raw)
In-Reply-To: <166843574651.160660.16747506894761495587.stgit@klimt.1015granger.net>
On Mon, 14 Nov 2022 09:36:39 -0500
Chuck Lever <chuck.lever@oracle.com> wrote:
> drivers/infiniband/core/cm_trace.h | 2
> drivers/infiniband/core/cma_trace.h | 2
> fs/nfs/nfs4trace.h | 6 -
> fs/nfs/nfstrace.h | 6 -
> include/trace/events/fs.h | 122 -----------
> include/trace/events/nfs.h | 375 -----------------------------------
> include/trace/events/rdma.h | 168 ----------------
> include/trace/events/rpcgss.h | 2
> include/trace/events/rpcrdma.h | 4
> include/trace/events/sunrpc.h | 2
> include/trace/events/sunrpc_base.h | 18 --
> include/trace/include/fs.h | 122 +++++++++++
> include/trace/include/nfs.h | 375 +++++++++++++++++++++++++++++++++++
> include/trace/include/rdma.h | 168 ++++++++++++++++
> include/trace/include/sunrpc.h | 18 ++
I'm not so sure I like the "include/trace/include" name. But kernel
developers are known for sucky naming conventions :-p
How about one of:
include/trace/linux/
include/trace/misc/
include/trace/ext/
include/trace/helpers/
?
-- Steve
next prev parent reply other threads:[~2022-11-14 15:01 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 [this message]
2022-11-14 15:03 ` Steven Rostedt
2022-11-14 15:13 ` Chuck Lever III
2022-11-14 15:18 ` 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=20221114100214.55848d8c@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