All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Brian Gix <brian.gix@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, brian.gix@intel.com,
	inga.stotland@intel.com
Subject: Re: [PATCH BlueZ v3 1/2] mesh: Fix uninitialized memory usage
Date: Tue, 14 Mar 2023 21:40:18 +0000	[thread overview]
Message-ID: <167883001806.25944.4701946410337864742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313231152.59147-1-brian.gix@gmail.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Brian Gix <brian.gix@gmail.com>:

On Mon, 13 Mar 2023 16:11:51 -0700 you wrote:
> When attempting to cancel an unknown Scan request structure must be
> NULL initialized.
> ---
>  mesh/manager.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - [BlueZ,v3,1/2] mesh: Fix uninitialized memory usage
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5934f133d44a
  - [BlueZ,v3,2/2] mesh: Loopback unprovisioned beacons
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7c0fb2fefb6a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-03-14 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 23:11 [PATCH BlueZ v3 1/2] mesh: Fix uninitialized memory usage Brian Gix
2023-03-13 23:11 ` [PATCH BlueZ v3 2/2] mesh: Loopback unprovisioned beacons Brian Gix
2023-03-14  0:19 ` [BlueZ,v3,1/2] mesh: Fix uninitialized memory usage bluez.test.bot
2023-03-14 21:40 ` patchwork-bot+bluetooth [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=167883001806.25944.4701946410337864742.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=brian.gix@gmail.com \
    --cc=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 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.