From: Namhyung Kim <namhyung@kernel.org>
To: Tanushree Shah <tshah@linux.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
jolsa@kernel.org, adrian.hunter@intel.com, vmolnaro@redhat.com,
mpetlan@redhat.com, tmricht@linux.ibm.com, maddy@linux.ibm.com,
irogers@google.com, linux-perf-users@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, atrajeev@linux.ibm.com,
hbathini@linux.ibm.com, Tejas.Manhas1@ibm.com,
Tanushree.Shah@ibm.com, Shivani.Nittor@ibm.com
Subject: Re: [PATCH] perf data convert json: Fix trace_seq memory leak in process_sample_event()
Date: Tue, 7 Jul 2026 23:05:24 -0700 [thread overview]
Message-ID: <ak3opN58uZ1UJzfs@google.com> (raw)
In-Reply-To: <845be1b6-8e56-46fa-a258-5b0033fac474@linux.ibm.com>
On Tue, Jul 07, 2026 at 07:36:06PM +0530, Tanushree Shah wrote:
> Hi Namhyung,
> The only change I had planned for v2 was the fix for the pre-existing issue,
> which has now already been merged separately upstream.
>
> https://github.com/torvalds/linux/commit/2857a5dca750ea989c6fb70b4c14e801e4b7b4ad
>
> Please let me know if there is any additional change you would like me to
> include in v2.
Oh, nevermind then. I'll process this.
Thanks,
Namhyung
next prev parent reply other threads:[~2026-07-08 6:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 6:55 [PATCH] perf data convert json: Fix trace_seq memory leak in process_sample_event() Tanushree Shah
2026-06-04 7:06 ` sashiko-bot
2026-06-04 16:10 ` Tanushree Shah
2026-06-04 21:29 ` Arnaldo Carvalho de Melo
2026-06-11 11:53 ` Tanushree Shah
2026-07-01 21:20 ` Namhyung Kim
2026-07-02 7:16 ` Tanushree Shah
2026-07-03 23:59 ` Namhyung Kim
2026-07-07 14:06 ` Tanushree Shah
2026-07-08 6:05 ` Namhyung Kim [this message]
2026-07-08 19:25 ` Namhyung Kim
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=ak3opN58uZ1UJzfs@google.com \
--to=namhyung@kernel.org \
--cc=Shivani.Nittor@ibm.com \
--cc=Tanushree.Shah@ibm.com \
--cc=Tejas.Manhas1@ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpetlan@redhat.com \
--cc=tmricht@linux.ibm.com \
--cc=tshah@linux.ibm.com \
--cc=vmolnaro@redhat.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