linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: "shuah@kernel.org" <shuah@kernel.org>,
	"mhiramat@kernel.org" <mhiramat@kernel.org>,
	Ching-lin Yu <chinglinyu@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"linux-trace-kernel@vger.kernel.org" 
	<linux-trace-kernel@vger.kernel.org>,
	"lkp@intel.com" <lkp@intel.com>, Nadav Amit <namit@vmware.com>,
	"oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>,
	Alexey Makhalov <amakhalov@vmware.com>,
	"er.ajay.kaher@gmail.com" <er.ajay.kaher@gmail.com>,
	"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
	Tapas Kundu <tkundu@vmware.com>,
	Vasavi Sirnapalli <vsirnapalli@vmware.com>
Subject: Re: [PATCH v5 02/10] eventfs: Implement tracefs_inode_cache
Date: Wed, 26 Jul 2023 17:39:18 -0400	[thread overview]
Message-ID: <20230726173918.107908a3@rorschach.local.home> (raw)
In-Reply-To: <0FE7065F-6536-4311-AF41-4ABBD8E3ECF8@vmware.com>

On Wed, 26 Jul 2023 18:45:34 +0000
Ajay Kaher <akaher@vmware.com> wrote:

> Ok, I will move this to v6 04/10.
> Let me know once you will complete the review of v5.

OK, I finished my review. Mostly more nits. Hopefully v6 will be what I
pull into linux-next.

-- Steve

  reply	other threads:[~2023-07-26 21:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 19:36 [PATCH v5 00/10] tracing: introducing eventfs Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 01/10] tracing: Require all trace events to have a TRACE_SYSTEM Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 02/10] eventfs: Implement tracefs_inode_cache Ajay Kaher
2023-07-25 23:06   ` Steven Rostedt
2023-07-26 18:45     ` Ajay Kaher
2023-07-26 21:39       ` Steven Rostedt [this message]
2023-07-22 19:36 ` [PATCH v5 03/10] tracefs: Rename and export some tracefs functions Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 04/10] eventfs: Implement eventfs dir creation functions Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 05/10] eventfs: Implement eventfs file add functions Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 06/10] eventfs: Implement eventfs lookup, read, open functions Ajay Kaher
2023-07-26 20:28   ` Steven Rostedt
2023-07-26 20:51   ` Steven Rostedt
2023-07-22 19:37 ` [PATCH v5 07/10] eventfs: Implement functions to create files and dirs when accessed Ajay Kaher
2023-07-26 20:34   ` Steven Rostedt
2023-07-22 19:37 ` [PATCH v5 08/10] eventfs: Implement removal of meta data from eventfs Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 09/10] eventfs: Move tracing/events to eventfs Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 10/10] test: ftrace: Fix kprobe test for eventfs Ajay Kaher

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=20230726173918.107908a3@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=akaher@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=chinglinyu@google.com \
    --cc=er.ajay.kaher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mhiramat@kernel.org \
    --cc=namit@vmware.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=srivatsa@csail.mit.edu \
    --cc=tkundu@vmware.com \
    --cc=vsirnapalli@vmware.com \
    /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).