From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] org.bluez.Gatt: Add org.bluez.Error.ImproperlyConfigured error to WriteValue
Date: Mon, 29 Apr 2024 14:50:30 +0000 [thread overview]
Message-ID: <171440223013.10266.7151781521429895730.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240426144826.2608852-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 26 Apr 2024 10:48:25 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Some attributes may require to generate
> BT_ERROR_CCC_IMPROPERLY_CONFIGURED when its CCC is not properly
> configured so this adds the possibility to generate it by replying with
> org.bluez.Error.ImproperlyConfigured error to WriteValue.
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] org.bluez.Gatt: Add org.bluez.Error.ImproperlyConfigured error to WriteValue
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=129b19166304
- [BlueZ,v1,2/2] gatt-database: Implement support to org.bluez.Error.ImproperlyConfigured
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9b29784717f4
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:[~2024-04-29 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 14:48 [PATCH BlueZ v1 1/2] org.bluez.Gatt: Add org.bluez.Error.ImproperlyConfigured error to WriteValue Luiz Augusto von Dentz
2024-04-26 14:48 ` [PATCH BlueZ v1 2/2] gatt-database: Implement support to org.bluez.Error.ImproperlyConfigured Luiz Augusto von Dentz
2024-04-26 17:09 ` [BlueZ,v1,1/2] org.bluez.Gatt: Add org.bluez.Error.ImproperlyConfigured error to WriteValue bluez.test.bot
2024-04-29 14:50 ` 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=171440223013.10266.7151781521429895730.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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.