public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Gix@ci.codeaurora.org, Brian <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	inga.stotland@intel.com
Subject: Re: [PATCH BlueZ 0/4] Mesh demon switched to using kernel Mesh MGMT
Date: Thu, 22 Sep 2022 21:20:15 +0000	[thread overview]
Message-ID: <166388161589.29143.11388511112936355434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220922203852.494315-1-brian.gix@intel.com>

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



      parent reply	other threads:[~2022-09-22 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 20:38 [PATCH BlueZ 0/4] Mesh demon switched to using kernel Mesh MGMT Brian Gix
2022-09-22 20:38 ` [PATCH BlueZ 1/4] mgmt: Add support for Mesh in the kernel Brian Gix
2022-09-22 21:32   ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 20:38 ` [PATCH BlueZ 2/4] lib: Add defines of new MGMT opcodes and events Brian Gix
2022-09-22 20:38 ` [PATCH BlueZ 3/4] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 20:38 ` [PATCH BlueZ 4/4] mesh: Add new kernel MGMT based IO transport Brian Gix
2022-09-22 21:20 ` 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=166388161589.29143.11388511112936355434.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=Gix@ci.codeaurora.org \
    --cc=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox