From: patchwork-bot+bluetooth@kernel.org
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH 0/3] Add Mesh functionality to net/bluetooth
Date: Fri, 01 Apr 2022 17:30:12 +0000 [thread overview]
Message-ID: <164883421225.6587.11737123964714497714.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220331180749.456913-1-brian.gix@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Thu, 31 Mar 2022 11:07:46 -0700 you wrote:
> Housekeeping and implementation.
>
> Brian Gix (3):
> Bluetooth: Keep MGMT pending queue ordered FIFO
> Bluetooth: Implement support for Mesh
> Bluetooth: Add experimental wrapper for MGMT based mesh
>
> [...]
Here is the summary with links:
- [1/3] Bluetooth: Keep MGMT pending queue ordered FIFO
https://git.kernel.org/bluetooth/bluetooth-next/c/2598fe7291d8
- [2/3] Bluetooth: Implement support for Mesh
(no matching commit)
- [3/3] Bluetooth: Add experimental wrapper for MGMT based mesh
(no matching commit)
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-04-01 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 18:07 [PATCH 0/3] Add Mesh functionality to net/bluetooth Brian Gix
2022-03-31 18:07 ` [PATCH 1/3] Bluetooth: Keep MGMT pending queue ordered FIFO Brian Gix
2022-03-31 19:13 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-03-31 18:07 ` [PATCH 2/3] Bluetooth: Implement support for Mesh Brian Gix
2022-03-31 18:07 ` [PATCH 3/3] Bluetooth: Add experimental wrapper for MGMT based mesh Brian Gix
2022-04-01 17:30 ` 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=164883421225.6587.11737123964714497714.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.