Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ 0/1] mesh: Use correct net_id in ctl_received
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <165662101345.30460.6134404687466381568.git-patchwork-notify@kernel.org>
Date:   Thu, 30 Jun 2022 20:30:13 +0000
References: <VI1PR09MB42395E20CFD614E52F3BC496E3BA9@VI1PR09MB4239.eurprd09.prod.outlook.com>
In-Reply-To: <VI1PR09MB42395E20CFD614E52F3BC496E3BA9@VI1PR09MB4239.eurprd09.prod.outlook.com>
To:     Isak Westin <isak.westin@hotmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Thu, 30 Jun 2022 09:29:18 +0200 you wrote:
> Hi,
> 
> I had an issue that the mesh-daemon local node never responded to friend
> requests from a low-power node. After some debugging, I found that the
> net_key_id passed to the ctl_received function was always uninitialized.
> It seems like the wrong variable was passed to the function.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] mesh: Use correct net_id for received CTL messages
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=be7ebf29b370

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