From: Nick Clifton <nickc@redhat.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 0/2] libsframe: fix some memory leaks
Date: Fri, 23 Dec 2022 09:55:59 +0000 [thread overview]
Message-ID: <36a98cc3-d5af-30c8-2455-243162c3bfd2@redhat.com> (raw)
In-Reply-To: <20221222225457.1095930-1-indu.bhagat@oracle.com>
Hi Indu,
> This patch set fixes some memory leaks in the libsframe and it's testsuite.
Patch series approved. Please apply.
Would you be interested in becoming an official maintainer for the libsframe
code ? That way you can approve your own patches - as long as they are specific
to libsframe of course.
Cheers
Nick
next prev parent reply other threads:[~2022-12-23 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 22:54 Indu Bhagat
2022-12-22 22:54 ` [PATCH 1/2] libsframe: fix a memory leak in sframe_decode Indu Bhagat
2022-12-22 22:54 ` [PATCH 2/2] libsframe: testsuite: fix memory leaks in testcases Indu Bhagat
2022-12-23 9:55 ` Nick Clifton [this message]
2022-12-23 15:35 ` [PATCH 0/2] libsframe: fix some memory leaks Indu Bhagat
2022-12-23 15:39 ` Nick Clifton
2022-12-23 14:22 ` libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks) Mark Wielaard
2022-12-23 14:41 ` Frank Ch. Eigler
2022-12-23 16:06 ` Mark Wielaard
2022-12-23 15:24 ` Indu Bhagat
2022-12-23 16:13 ` Mark Wielaard
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=36a98cc3-d5af-30c8-2455-243162c3bfd2@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).