From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v2 0/2] mesh: Valgrind Clean-up
Date: Sat, 16 May 2020 15:56:28 +0000 [thread overview]
Message-ID: <220533947be7b56c12013ac726b14a0370418575.camel@intel.com> (raw)
In-Reply-To: <20200516012742.573151-1-brian.gix@intel.com>
Patchset Applied
On Fri, 2020-05-15 at 18:27 -0700, Brian Gix wrote:
> These two patches address all known outstanding valgrind issues with the
> mesh daemon. The first patch (1/2) fixes actual memory leaks that will
> compound over time. The second patch (2/2) fixes less critical warnings
> that some memory wasn't entirely freed before exiting.
>
> v2: Fixed checkpatch errors
>
> Brian Gix (2):
> mesh: Fix valgrind memory leaks
> mesh: Fix valgrind memory leak warnings
>
> mesh/agent.c | 1 +
> mesh/mesh-config-json.c | 16 ++++++++--------
> mesh/mesh.c | 9 ++++++++-
> mesh/net-keys.c | 6 ++++++
> mesh/net-keys.h | 1 +
> mesh/net.c | 12 +++++++++++-
> mesh/net.h | 3 ++-
> mesh/node.c | 1 +
> 8 files changed, 38 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2020-05-16 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 1:27 [PATCH BlueZ v2 0/2] mesh: Valgrind Clean-up Brian Gix
2020-05-16 1:27 ` [PATCH BlueZ v2 1/2] mesh: Fix valgrind memory leaks Brian Gix
2020-05-20 7:42 ` Michał Lowas-Rzechonek
2020-05-16 1:27 ` [PATCH BlueZ v2 2/2] mesh: Fix valgrind memory leak warnings Brian Gix
2020-05-16 15:56 ` Gix, Brian [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=220533947be7b56c12013ac726b14a0370418575.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@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).