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/4] Mesh demon switched to using kernel Mesh MGMT
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <166388161589.29143.11388511112936355434.git-patchwork-notify@kernel.org>
Date:   Thu, 22 Sep 2022 21:20:15 +0000
References: <20220922203852.494315-1-brian.gix@intel.com>
In-Reply-To: <20220922203852.494315-1-brian.gix@intel.com>
To:     Gix@ci.codeaurora.org, Brian <brian.gix@intel.com>
Cc:     linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
        inga.stotland@intel.com
Precedence: bulk

Hello:

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

On Thu, 22 Sep 2022 13:38:48 -0700 you wrote:
> This patchset enables the mesh daemon (bluetooth-meshd) to use the new
> MGMT mesh opcodes and events to send and receive Mesh packets. By
> default, the daemon attempts to enable the experimental mesh
> functionality, and query the kernel for active mesh support before then
> enumerating the available controllers and selecting ojne that works.
> 
> If no kernel support is found, it will continue to use a raw HCI socket
> for mesh support.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/4] mgmt: Add support for Mesh in the kernel
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0454e2d09570
  - [BlueZ,2/4] lib: Add defines of new MGMT opcodes and events
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=721d5a8ae86d
  - [BlueZ,3/4] mesh: Improve PB-ADV timing for reliability
    (no matching commit)
  - [BlueZ,4/4] mesh: Add new kernel MGMT based IO transport
    (no matching commit)

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