From: "Eugene Mavick" <m@mavick.dev>
To: "Eugene Mavick" <m@mavick.dev>, "Will Deacon" <will@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Boqun Feng" <boqun@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Gary Guo" <gary@garyguo.net>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dennis Zhou" <dennis@kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Christoph Lameter" <cl@gentwo.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH 0/4] tracing: add ref_trace_final_put tracing
Date: Tue, 07 Jul 2026 14:18:38 +0800 [thread overview]
Message-ID: <DJS4CP5DU9UH.699SV5JGDXGN@mavick.dev> (raw)
In-Reply-To: <20260705-refcount-final-put-trace-v1-0-cdd0014626a9@mavick.dev>
I apologise for the duplicate patch series submission, I had resent the
v1 via b4 relay as it did not show up on lore.kernel.org for a
day, and I assumed the emails were lost.
next prev parent reply other threads:[~2026-07-07 6:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 23:19 [PATCH 0/4] tracing: add ref_trace_final_put tracing Eugene Mavick
2026-07-04 23:19 ` [PATCH 1/4] tracing: add ref_trace_final_put tracepoint Eugene Mavick
2026-07-06 13:33 ` Steven Rostedt
2026-07-06 13:36 ` Steven Rostedt
2026-07-04 23:19 ` [PATCH 2/4] refcount: " Eugene Mavick
2026-07-04 23:19 ` [PATCH 3/4] percpu-refcount: add ref_trace_final_put trace Eugene Mavick
2026-07-04 23:19 ` [PATCH 4/4] kunit: add test for ref_trace_final_put Eugene Mavick
2026-07-07 6:18 ` Eugene Mavick [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 0:36 [PATCH 0/4] tracing: add ref_trace_final_put tracing Eugene Mavick
2026-07-05 1:20 Eugene Mavick via B4 Relay
2026-07-05 1:20 ` Eugene Mavick
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=DJS4CP5DU9UH.699SV5JGDXGN@mavick.dev \
--to=m@mavick.dev \
--cc=akpm@linux-foundation.org \
--cc=boqun@kernel.org \
--cc=cl@gentwo.org \
--cc=dennis@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.