From: Steven Rostedt <rostedt@goodmis.org>
To: 高翔 <gaoxiang17@xiaomi.com>
Cc: "Masami Hiramatsu" <mhiramat@kernel.org>,
"Vincent Donnefort" <vdonnefort@google.com>,
"Xiang Gao" <gxxa03070307@gmail.com>,
"Donggeun Yoo" <donggeunyoo.kernel@gmail.com>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Lorenzo Stoakes" <ljs@kernel.org>, "gao xu" <gaoxu2@honor.com>,
印闯 <yinchuang1@xiaomi.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External Mail]Re: [PATCH v4 1/2] tracing: add ring-buffer memory usage statistics in tracefs
Date: Sat, 24 Oct 2026 08:04:23 -0400 [thread overview]
Message-ID: <20261024080423.069948c9@fedora> (raw)
In-Reply-To: <4f9c82054c46459688d9a69df58293d1@xiaomi.com>
On Sat, 24 Oct 2026 06:59:28 +0000
高翔 <gaoxiang17@xiaomi.com> wrote:
> Hi Steven,
>
>
> Just checking if you had a chance to look at this one. Any estimate on
> when you might be able to review it?
Sorry. You sent this out when I started my travels (Sept 15 - Oct 10th)
and when I got back I had a lot bug fixes to handle before new code,
and then the merge window opened. You're patches are not the only ones
that were postponed. Any new features that were sent after Sept 15th
are delayed to the next merge window.
-- Steve
next prev parent reply other threads:[~2026-10-24 12:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 11:27 [PATCH 0/2] tracing: add ring-buffer memory usage statistics Xiang Gao
2026-09-05 11:27 ` [PATCH 1/2] tracing: add ring-buffer memory usage statistics in tracefs Xiang Gao
2026-09-07 9:26 ` Vincent Donnefort
2026-09-05 11:27 ` [PATCH 2/2] tracing: add per-CPU " Xiang Gao
2026-09-11 15:50 ` [PATCH v2 0/2] tracing: add ring-buffer memory usage statistics Xiang Gao
2026-09-11 15:50 ` [PATCH v2 1/2] tracing: add ring-buffer memory usage statistics in tracefs Xiang Gao
2026-09-13 16:37 ` Donggeun Yoo
2026-09-11 15:50 ` [PATCH v2 2/2] tracing: add per-CPU " Xiang Gao
2026-09-16 6:33 ` [PATCH v3 0/2] tracing: add ring-buffer memory usage statistics Xiang Gao
2026-09-16 6:33 ` [PATCH v3 1/2] tracing: add ring-buffer memory usage statistics in tracefs Xiang Gao
2026-09-16 6:33 ` [PATCH v3 2/2] tracing: add per-CPU " Xiang Gao
2026-09-21 11:30 ` [PATCH v4 0/2] tracing: add ring-buffer memory usage statistics Xiang Gao
2026-09-21 11:30 ` [PATCH v4 1/2] tracing: add ring-buffer memory usage statistics in tracefs Xiang Gao
2026-09-22 9:41 ` Vincent Donnefort
2026-09-24 1:27 ` Masami Hiramatsu
2026-09-24 8:54 ` Vincent Donnefort
2026-09-25 1:09 ` Masami Hiramatsu
[not found] ` <cb0090dd1ad84a5b833e9323fd2b05d5@xiaomi.com>
[not found] ` <51b25b1c996d4412a0c43d94acea98df@xiaomi.com>
2026-10-14 13:18 ` [External Mail]Re: " Steven Rostedt
[not found] ` <4f9c82054c46459688d9a69df58293d1@xiaomi.com>
2026-10-24 12:04 ` Steven Rostedt [this message]
2026-09-21 11:30 ` [PATCH v4 2/2] tracing: add per-CPU " Xiang Gao
2026-09-22 9:42 ` Vincent Donnefort
2026-09-24 1:36 ` Masami Hiramatsu
2026-09-11 17:22 ` [PATCH 0/2] tracing: add ring-buffer memory usage statistics Vincent Donnefort
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=20261024080423.069948c9@fedora \
--to=rostedt@goodmis.org \
--cc=donggeunyoo.kernel@gmail.com \
--cc=gaoxiang17@xiaomi.com \
--cc=gaoxu2@honor.com \
--cc=gxxa03070307@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=vdonnefort@google.com \
--cc=yinchuang1@xiaomi.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
all inboxes | Powered by JetHome®