[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230411124826.04d19759@gandalf.local.home>
Date: Tue, 11 Apr 2023 12:48:26 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Tze-nan Wu <Tze-nan.Wu@...iatek.com>
Cc: <mhiramat@...nel.org>, <bobule.chang@...iatek.com>,
<wsd_upstream@...iatek.com>, <cheng-jui.wang@...iatek.com>,
<npiggin@...il.com>, <stable@...r.kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-trace-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH v3] ring-buffer: Prevent inconsistent operation on
cpu_buffer->resize_disabled
On Tue, 11 Apr 2023 12:44:03 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> Please have each new patch be a new thread, and not a Cc to the previous
Should have been "reply to the previous" :-p
-- Steve
> version of the patch. As it makes it hard to find in INBOXs.
Powered by blists - more mailing lists