From: patchwork-bot+bluetooth@kernel.org
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
inga.stotland@intel.com
Subject: Re: [PATCH BlueZ v5 0/2] Mesh demon switched to using kernel Mesh MGMT
Date: Mon, 26 Sep 2022 20:20:15 +0000 [thread overview]
Message-ID: <166422361598.9012.17342942678830979726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923180018.815614-1-brian.gix@intel.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Brian Gix <brian.gix@intel.com>:
On Fri, 23 Sep 2022 11:00:16 -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,v5,1/2] mesh: Improve PB-ADV timing for reliability
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=491be481a91c
- [BlueZ,v5,2/2] mesh: Add new kernel MGMT based IO transport
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9966cb8b6999
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-26 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 18:00 [PATCH BlueZ v5 0/2] Mesh demon switched to using kernel Mesh MGMT Brian Gix
2022-09-23 18:00 ` [PATCH BlueZ v5 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-23 19:24 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-23 18:00 ` [PATCH BlueZ v5 2/2] mesh: Add new kernel MGMT based IO transport Brian Gix
2022-09-26 20: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=166422361598.9012.17342942678830979726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.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 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.