All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "prathyusha.n@samsung.com" <prathyusha.n@samsung.com>,
	"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v2 0/3] mesh: Fix various valgrind identified problems
Date: Wed, 4 Dec 2019 18:01:12 +0000	[thread overview]
Message-ID: <814789dacd5a5e71712634e835317ffe923f5a7d.camel@intel.com> (raw)
In-Reply-To: <20191203210410.25548-1-brian.gix@intel.com>

Patchset Applied

On Tue, 2019-12-03 at 13:04 -0800, Brian Gix wrote:
> This patchset addresses a few valgrind identified errors, including some
> instances where memory was used after freeing.  All three patches relate
> to the memory allocated for Provisioning purposes.
> 
> This includes the patch from Prathyusha that fixes close indication.
> 
> Brian Gix (2):
>   mesh: Rearrange PB-ACK for possible session close
>   mesh: Fix memory leak in Join() API call
> 
> Prathyusha N (1):
>   mesh: Fix to send close indication on timeout
> 
>  mesh/mesh.c          |  7 +++++--
>  mesh/net.c           |  1 -
>  mesh/pb-adv.c        | 10 ++++------
>  mesh/prov-acceptor.c |  1 +
>  4 files changed, 10 insertions(+), 9 deletions(-)
> 

      parent reply	other threads:[~2019-12-04 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 21:04 [PATCH BlueZ v2 0/3] mesh: Fix various valgrind identified problems Brian Gix
2019-12-03 21:04 ` [PATCH BlueZ v2 1/3] mesh: Fix to send close indication on timeout Brian Gix
2019-12-03 21:04 ` [PATCH BlueZ v2 2/3] mesh: Rearrange PB-ACK for possible session close Brian Gix
2019-12-03 21:04 ` [PATCH BlueZ v2 3/3] mesh: Fix memory leak in Join() API call Brian Gix
2019-12-04 18:01 ` 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=814789dacd5a5e71712634e835317ffe923f5a7d.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=prathyusha.n@samsung.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 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.