All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michalis Niarchos <michael.niarchos@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] perf tools: Fix memory issues
Date: Thu, 6 Aug 2026 14:17:40 +0200	[thread overview]
Message-ID: <dd06f979-ac82-4331-b888-c0ff2fea7cc9@gmail.com> (raw)
In-Reply-To: <anQXwT3fD5oZDWz0@google.com>

Hi,

Confirming that the issues addressed by these patches have already been
fixed in perf-tools-next. Please disregard them.

Thanks for pointing me to the perf-tools-next tree — I was comparing
against mainline and hadn't checked there.

Regards,
Michalis

      reply	other threads:[~2026-08-06 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 13:51 [PATCH v3 0/3] perf tools: Fix memory issues Michalis Niarchos via B4 Relay
2026-08-03 13:51 ` Michalis Niarchos
2026-08-03 13:51 ` [PATCH v3 1/3] perf tools: Fix memory leak in cmd_kvm() Michalis Niarchos via B4 Relay
2026-08-03 13:51   ` Michalis Niarchos
2026-08-03 13:51 ` [PATCH v3 2/3] perf tools: Fix double free and memory leak issues Michalis Niarchos via B4 Relay
2026-08-03 13:51   ` Michalis Niarchos
2026-08-03 13:51 ` [PATCH v3 3/3] perf tools: Fix memory leak in cmd_kvm() Michalis Niarchos via B4 Relay
2026-08-03 13:51   ` Michalis Niarchos
2026-08-06  5:12 ` [PATCH v3 0/3] perf tools: Fix memory issues Namhyung Kim
2026-08-06 12:17   ` Michalis Niarchos [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=dd06f979-ac82-4331-b888-c0ff2fea7cc9@gmail.com \
    --to=michael.niarchos@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@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 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.