From: patchwork-bot+bluetooth@kernel.org
To: Tedd Ho-Jeong An <hj.tedd.an@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ PATCH] tools/mgmt-tester: Add test case for scan response data is not updating
Date: Wed, 22 Jun 2022 06:30:12 +0000 [thread overview]
Message-ID: <165587941276.28820.1996698265401619013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220621201054.66411-1-hj.tedd.an@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 21 Jun 2022 13:10:54 -0700 you wrote:
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>
> This patch adds a test case to test if the scan response data is updated
> when the following scenarios are performed.
>
> 1. Add Extended Advertising Parameters Command
> 2. Add Extended Advertising Data Command w/ Scan Resp Data
> 3. Remove Advertising Command
> 4. Add Extended Advertising Parameters Command
> 5. Add Extended Advertising Data Command w/ Scan Resp Data
> 6. Host should set Scan Resp Data
>
> [...]
Here is the summary with links:
- [BlueZ] tools/mgmt-tester: Add test case for scan response data is not updating
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b8b3277ba387
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-06-22 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 20:10 [BlueZ PATCH] tools/mgmt-tester: Add test case for scan response data is not updating Tedd Ho-Jeong An
2022-06-21 22:11 ` [BlueZ] " bluez.test.bot
2022-06-22 6: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=165587941276.28820.1996698265401619013.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hj.tedd.an@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;
as well as URLs for NNTP newsgroup(s).