From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2 0/2] tracing: Fix patches with goto out
Date: Wed, 25 Dec 2024 17:25:40 -0500 [thread overview]
Message-ID: <20241225222540.685602520@goodmis.org> (raw)
In my patch series:
https://lore.kernel.org/linux-trace-kernel/20241219201158.193821672@goodmis.org/
Of switching over to the guard logic. I missed a removal of a goto out in
the osnoise, but fixed it in the stack trace patch.
Since the patches are supposed to be agnostic from each other, fix the
osnoise patch, and remove the fix from the stack trace patch.
next reply other threads:[~2024-12-25 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 22:25 Steven Rostedt [this message]
2024-12-25 22:25 ` [PATCH v2 1/2] [PATCH] tracing: Switch trace_osnoise.c code over to use guard() and __free() Steven Rostedt
2024-12-25 22:25 ` [PATCH v2 2/2] [PATCH] tracing: Switch trace_stack.c code over to use guard() Steven Rostedt
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=20241225222540.685602520@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 \
/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