Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: 高翔 <gaoxiang17@xiaomi.com>
Cc: "Xiang Gao" <gxxa03070307@gmail.com>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"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][RFC] tracing: aggregate ring-buffer memory statistics
Date: Thu, 27 Aug 2026 11:35:13 -0400	[thread overview]
Message-ID: <20260827113513.7355403f@gandalf.local.home> (raw)
In-Reply-To: <93406afe7c684d649f11b05d7b6b7b7b@xiaomi.com>

On Thu, 27 Aug 2026 14:25:24 +0000
高翔 <gaoxiang17@xiaomi.com> wrote:

> Hi Steven.
> 

It's good to ping after one week of no responses. RFCs tend to get low
priority and are looked at after fixes and other code needs to be reviewed.

But I'll take a look now anyway as I just finished sending out fixes.

-- Steve

  parent reply	other threads:[~2026-08-27 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 14:10 [RFC] tracing: aggregate ring-buffer memory statistics Xiang Gao
     [not found] ` <93406afe7c684d649f11b05d7b6b7b7b@xiaomi.com>
2026-08-27 15:35   ` Steven Rostedt [this message]
2026-08-27 15:38 ` Steven Rostedt
     [not found]   ` <15c244f5bc8f4858b8ffa2974a46d009@xiaomi.com>
     [not found]     ` <88d476d443e74672957a5e0d1f8bf9ba@xiaomi.com>
2026-09-02 13:15       ` [External Mail]Re: " Steven Rostedt
     [not found]         ` <ca552a4c093b4498b2e308d266d5ab6f@xiaomi.com>
2026-09-02 14:39           ` Steven Rostedt
     [not found]             ` <e4c4d3f20b1445869ba329e561f6d042@xiaomi.com>
2026-09-02 14:48               ` 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=20260827113513.7355403f@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --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=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