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 1/3] mgmt-api: Update Device Found Event documentation
Date: Wed, 21 Jun 2023 22:10:25 +0000 [thread overview]
Message-ID: <168738542521.32529.13902091080525146600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230620204053.643608-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 Tue, 20 Jun 2023 13:40:51 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This updates Device Found Event documentation to mention the new flag
> introduced to track when the event is generated due a interleaved Scan
> Response that couldn't be merged.
> ---
> doc/mgmt-api.txt | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [BlueZ,1/3] mgmt-api: Update Device Found Event documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=98383b917a43
- [BlueZ,2/3] monitor: Add missing flags to MGMT Device Found Event
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=741a04aba0c3
- [BlueZ,3/3] adapter: Handle Device Found Event with Scan Response flag
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c8235156c31b
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-06-21 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 20:40 [PATCH BlueZ 1/3] mgmt-api: Update Device Found Event documentation Luiz Augusto von Dentz
2023-06-20 20:40 ` [PATCH BlueZ 2/3] monitor: Add missing flags to MGMT Device Found Event Luiz Augusto von Dentz
2023-06-20 20:40 ` [PATCH BlueZ 3/3] adapter: Handle Device Found Event with Scan Response flag Luiz Augusto von Dentz
2023-06-20 22:31 ` [BlueZ,1/3] mgmt-api: Update Device Found Event documentation bluez.test.bot
2023-06-21 22: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=168738542521.32529.13902091080525146600.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox