From: "Tze-nan Wu (吳澤南)" <Tze-nan.Wu@mediatek.com>
To: "mhiramat@kernel.org" <mhiramat@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Cheng-Jui Wang (王正睿)" <Cheng-Jui.Wang@mediatek.com>,
wsd_upstream <wsd_upstream@mediatek.com>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"Bobule Chang (張弘義)" <bobule.chang@mediatek.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"npiggin@gmail.com" <npiggin@gmail.com>
Subject: Re: [PATCH v3] ring-buffer: Prevent inconsistent operation on cpu_buffer->resize_disabled
Date: Fri, 14 Apr 2023 01:16:43 +0000 [thread overview]
Message-ID: <3747eb90487f6eb9cd2f6ff84208c08d4b958bd9.camel@mediatek.com> (raw)
In-Reply-To: <20230410073512.13362-1-Tze-nan.Wu@mediatek.com>
In case those who are following this thread but are not included in the
cc list, the v4 patch cannot be easily found by them due to the tile of
the newer patch had been changed.
Let my put a link here:
https://lore.kernel.org/lkml/20230412112401.25081-1-Tze-nan.Wu@mediatek.com/
prev parent reply other threads:[~2023-04-14 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 5:22 [PATCH] ring-buffer: Prevent inconsistent operation on cpu_buffer->resize_disabled Tze-nan Wu
2023-04-08 8:35 ` kernel test robot
2023-04-08 12:20 ` kernel test robot
2023-04-09 2:46 ` [PATCH v2] " Tze-nan Wu
2023-04-09 12:30 ` Bagas Sanjaya
2023-04-10 1:35 ` Tze-nan Wu (吳澤南)
2023-04-10 7:35 ` [PATCH v3] " Tze-nan Wu
2023-04-11 16:44 ` Steven Rostedt
2023-04-11 16:48 ` Steven Rostedt
2023-04-12 2:27 ` Tze-nan Wu (吳澤南)
2023-04-12 2:32 ` Steven Rostedt
2023-04-14 1:16 ` Tze-nan Wu (吳澤南) [this message]
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=3747eb90487f6eb9cd2f6ff84208c08d4b958bd9.camel@mediatek.com \
--to=tze-nan.wu@mediatek.com \
--cc=Cheng-Jui.Wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bobule.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=wsd_upstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).