From: patchwork-bot+bluetooth@kernel.org
To: Inga Stotland <inga.stotland@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, brian.gix@gmail.com,
brian.gix@intel.com
Subject: Re: [PATCH BlueZ v2 1/2] tools/mesh-cfgclient: Prevent storing duplicate models
Date: Fri, 17 Mar 2023 20:30:18 +0000 [thread overview]
Message-ID: <167908501859.28511.1166223350843990916.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230316213312.159370-1-inga.stotland@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Brian Gix <brian.gix@gmail.com>:
On Thu, 16 Mar 2023 14:33:11 -0700 you wrote:
> This fixes the situation when subsequent requests to get a node
> composition result in appending element's model list with duplicate models.
> This adds a check for a presence of a model on an element when attempting
> to add a new model ID to a model list on this element.
> ---
> tools/mesh/mesh-db.c | 17 ++++++++++++-----
> tools/mesh/remote.c | 9 +++++++++
> 2 files changed, 21 insertions(+), 5 deletions(-)
Here is the summary with links:
- [BlueZ,v2,1/2] tools/mesh-cfgclient: Prevent storing duplicate models
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bc961998a842
- [BlueZ,v2,2/2] tools/mesh-cfgclient: Auto request own composition data
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=551a0c80ab33
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:[~2023-03-17 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 21:33 [PATCH BlueZ v2 1/2] tools/mesh-cfgclient: Prevent storing duplicate models Inga Stotland
2023-03-16 21:33 ` [PATCH BlueZ v2 2/2] tools/mesh-cfgclient: Auto request own composition data Inga Stotland
2023-03-16 23:24 ` [BlueZ,v2,1/2] tools/mesh-cfgclient: Prevent storing duplicate models bluez.test.bot
2023-03-17 20: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=167908501859.28511.1166223350843990916.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@gmail.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox