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/4] mesh: Static Analysis clean-up
Date: Mon, 25 May 2020 14:15:41 +0000 [thread overview]
Message-ID: <837c5bd96fc3bf44e6bb791fbd2e4bab79556ba1.camel@intel.com> (raw)
In-Reply-To: <20200522211309.233824-1-brian.gix@intel.com>
Patchset Applied
On Fri, 2020-05-22 at 14:13 -0700, Brian Gix wrote:
> This patchset fixes static analysis identified issues in the
> mesh daemon.
>
> v2: Clean-up PB-ADV queue
>
>
> Brian Gix (4):
> mesh: Fix using uninitialized bytes
> mesh: Fix leaked mesh_net allocation
> mesh: Fix leaked message reference
> mesh: Destroy PB-ADV queue when provisioning done
>
> mesh/crypto.c | 1 +
> mesh/manager.c | 3 ++-
> mesh/node.c | 4 ++--
> mesh/pb-adv.c | 5 +++++
> 4 files changed, 10 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2020-05-25 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 21:13 [PATCH BlueZ v2 0/4] mesh: Static Analysis clean-up Brian Gix
2020-05-22 21:13 ` [PATCH BlueZ v2 1/4] mesh: Fix using uninitialized bytes Brian Gix
2020-05-22 21:13 ` [PATCH BlueZ v2 2/4] mesh: Fix leaked mesh_net allocation Brian Gix
2020-05-22 23:37 ` [BlueZ,v2,2/4] " bluez.test.bot
2020-05-22 21:13 ` [PATCH BlueZ v2 3/4] mesh: Fix leaked message reference Brian Gix
2020-05-22 23:37 ` [BlueZ,v2,3/4] " bluez.test.bot
2020-05-22 21:13 ` [PATCH BlueZ v2 4/4] mesh: Destroy PB-ADV queue when provisioning done Brian Gix
2020-05-22 23:37 ` [BlueZ,v2,4/4] " bluez.test.bot
2020-05-25 14:15 ` 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=837c5bd96fc3bf44e6bb791fbd2e4bab79556ba1.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).