[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231220075310.634672bc@gandalf.local.home>
Date: Wed, 20 Dec 2023 07:53:10 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Mark
Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Tzvetomir Stoyanov <tz.stoyanov@...il.com>,
Vincent Donnefort <vdonnefort@...gle.com>, Kent Overstreet
<kent.overstreet@...il.com>
Subject: Re: [PATCH v5 01/15] ring-buffer: Refactor ring buffer
implementation
On Wed, 20 Dec 2023 18:48:43 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> > From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@...il.com>
> >
> > In order to introduce sub-buffer size per ring buffer, some internal
> > refactoring is needed. As ring_buffer_print_page_header() will depend on
> > the trace_buffer structure, it is moved after the structure definition.
> >
> > Link: https://lore.kernel.org/linux-trace-devel/20211213094825.61876-2-tz.stoyanov@gmail.com
> >
>
> OK, but the title is too generic. Something like
> "Move ring_buffer_print_page_header() after ring_buffer_iter"
> will be preferable.
>
Yeah, I can update the subject. Thanks!
-- Steve
Powered by blists - more mailing lists