linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: axboe@kernel.dk, rostedt@goodmis.org, mhiramat@kernel.org,
	 mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
	 linux-block@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	 Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH v3 0/4] relayfs: misc changes
Date: Fri, 23 May 2025 07:42:17 +0800	[thread overview]
Message-ID: <CAL+tcoBUEpcyt3Vq8_f8Jyo3+1mLtdEH2QEf6nVAOYzRHitfNA@mail.gmail.com> (raw)
In-Reply-To: <20250522163418.f14da5eea065296d42ee3497@linux-foundation.org>

On Fri, May 23, 2025 at 7:34 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 23 May 2025 07:16:35 +0800 Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> > On Sun, May 18, 2025 at 10:57 AM Jason Xing <kerneljasonxing@gmail.com> wrote:
> > >
> > > From: Jason Xing <kernelxing@tencent.com>
> > >
> > > The series mostly focuses on the error counters which helps every user
> > > debug their own kernel module.
> > >
> > > ---
> > > Note: this series is made on top of this cleanup[1] and unmerged commit[2]
> > > [1]: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/log/?h=mm-nonmm-unstable
> > > [2]: https://lore.kernel.org/all/20250507134225.63248-1-kerneljasonxing@gmail.com/
> > >
> > > Jason Xing (4):
> > >   relayfs: support a counter tracking if per-cpu buffers is full
> > >   relayfs: introduce getting relayfs statistics function
> > >   blktrace: use rbuf->stats.full as a drop indicator in relayfs
> > >   relayfs: support a counter tracking if data is too big to write
> > >
> > >  include/linux/relay.h   | 19 ++++++++++++++-
> > >  kernel/relay.c          | 52 +++++++++++++++++++++++++++++++++++------
> > >  kernel/trace/blktrace.c | 22 ++---------------
> > >  3 files changed, 65 insertions(+), 28 deletions(-)
> >
> > Hi Andrew,
> >
> > Any comments on the series?
> >
>
> We're at -rc7 now, so I'll park this for consideration for -rc1.

Okay. IIUC, it seems probably two or three weeks later. I think I'll
keep track of the series and remind you at that time just in case you
might forget it :)

Thanks,
Jason

  reply	other threads:[~2025-05-22 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18  2:57 [PATCH v3 0/4] relayfs: misc changes Jason Xing
2025-05-18  2:57 ` [PATCH v3 1/4] relayfs: support a counter tracking if per-cpu buffers is full Jason Xing
2025-05-18  2:57 ` [PATCH v3 2/4] relayfs: introduce getting relayfs statistics function Jason Xing
2025-05-18  2:57 ` [PATCH v3 3/4] blktrace: use rbuf->stats.full as a drop indicator in relayfs Jason Xing
2025-05-18  2:57 ` [PATCH v3 4/4] relayfs: support a counter tracking if data is too big to write Jason Xing
2025-05-22 23:16 ` [PATCH v3 0/4] relayfs: misc changes Jason Xing
2025-05-22 23:34   ` Andrew Morton
2025-05-22 23:42     ` Jason Xing [this message]
2025-05-23  2:39 ` Masami Hiramatsu
2025-05-23  2:44   ` Jason Xing

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=CAL+tcoBUEpcyt3Vq8_f8Jyo3+1mLtdEH2QEf6nVAOYzRHitfNA@mail.gmail.com \
    --to=kerneljasonxing@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=kernelxing@tencent.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).