From: patchwork-bot+bluetooth@kernel.org
To: Isak Westin <isak.westin@hotmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/3] Mesh model publication fixes according to mesh profile
Date: Thu, 22 Sep 2022 21:10:16 +0000 [thread overview]
Message-ID: <166388101637.22480.18300225277952361024.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <VI1PR09MB42396AFF2009109A4318E51AE34F9@VI1PR09MB4239.eurprd09.prod.outlook.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Brian Gix <brian.gix@intel.com>:
On Wed, 21 Sep 2022 10:39:38 +0200 you wrote:
> Hi,
>
> I am testing the BlueZ Mesh stack with PTS (MESH and MMDL layers) and
> there are some parts of the mesh stack that are not behaving according
> to the mesh profile. Here are fixes to a few of them I encountered
> when testing the model publication procedures (MESH/NODE/CFG/MP).
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] mesh: Add interface output filter
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a76ff5879b75
- [BlueZ,2/3] mesh: Do not accept publication for unbound appkey
(no matching commit)
- [BlueZ,3/3] mesh: Remove RFU check for publication set
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c9fadca7eba4
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-22 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 8:39 [PATCH BlueZ 0/3] Mesh model publication fixes according to mesh profile Isak Westin
2022-09-22 21:10 ` 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=166388101637.22480.18300225277952361024.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=isak.westin@hotmail.com \
--cc=linux-bluetooth@vger.kernel.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.