public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 v7 0/2] Add Mesh functionality to net/bluetooth
Date: Thu, 01 Sep 2022 22:00:42 +0000	[thread overview]
Message-ID: <166206964233.4836.4376426391398219351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220901191914.22706-1-brian.gix@intel.com>

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  1 Sep 2022 12:19:12 -0700 you wrote:
> Housekeeping and implementation
> 
> v2: Add checking for Packet Ownership when querying Tx queue state
>     Add cleanup of Tx queue when MGMT socket closes
> 
> v3: Fix CI complaints
> 
> [...]

Here is the summary with links:
  - [v7,1/2] Bluetooth: Implement support for Mesh
    https://git.kernel.org/bluetooth/bluetooth-next/c/6db7da4c50f0
  - [v7,2/2] Bluetooth: Add experimental wrapper for MGMT based mesh
    https://git.kernel.org/bluetooth/bluetooth-next/c/45d33c081bcf

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-01 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 19:19 [PATCH v7 0/2] Add Mesh functionality to net/bluetooth Brian Gix
2022-09-01 19:19 ` [PATCH v7 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-09-01 20:01   ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-09-01 19:19 ` [PATCH v7 2/2] Bluetooth: Add experimental wrapper for MGMT based mesh Brian Gix
2022-09-01 22:00 ` 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=166206964233.4836.4376426391398219351.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox