linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] libtracecmd: fix memory leak on partial reverse iteration
Date: Fri, 21 Nov 2025 12:11:50 -0500	[thread overview]
Message-ID: <20251121121150.5f02faf4@gandalf.local.home> (raw)
In-Reply-To: <20251121134749.1530855-1-felix.moessbauer@siemens.com>


Nit, when sending patches, please capitalize the first word in the subject:

   [PATCH] libtracecmd: Fix memory leak on partial reverse iteration

(I updated this when pulling in your patch).

And you don't need the 1/1 for a single patch.

Thanks!

-- Steve

      parent reply	other threads:[~2025-11-21 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 13:47 [PATCH 1/1] libtracecmd: fix memory leak on partial reverse iteration Felix Moessbauer
2025-11-21 17:01 ` Steven Rostedt
2025-11-24  9:14   ` MOESSBAUER, Felix
2025-11-24 16:58     ` Steven Rostedt
2025-11-21 17:11 ` Steven Rostedt [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=20251121121150.5f02faf4@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=felix.moessbauer@siemens.com \
    --cc=linux-trace-devel@vger.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 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).