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 v2] tools/ioctl-tester - Add ioctl-tester
Date: Thu, 22 Sep 2022 01:10:22 +0000 [thread overview]
Message-ID: <166380902210.22214.8719483951038733963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921192826.102801-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 Wed, 21 Sep 2022 12:28:26 -0700 you wrote:
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>
> This patch adds ioctl-tester which tests the IOCTL commands.
>
> HCI Down
> Device List
> Device List - Invalid Param 1
> Device Info
> Reset Stat
> Set Link Mode - ACCEPT
> Set Link Mode - MASTER
> Set Pkt Type - DM
> Set Pkt Type - DH
> Set Pkt Type - HV
> Set Pkt Type - 2-DH
> Set Pkt Type - 2-DH
> Set Pkt Type - ALL
> Set ACL MTU - 1
> Set ACL MTU - 2
> Set SCO MTU - 1
> Set SCO MTU - 2
> Block BDADDR - Success
> Block BDADDR - Fail
> Unblock BDADDR - Success
> Unblock BDADDR - Fail
> Connection List - No Conn
> Connection List
> Connection Info
> Connection Info - No Connection
> Connection Info - Wrong Type
> Authentication Info - No Connection
> Authentication Info
>
> [...]
Here is the summary with links:
- [BlueZ,v2] tools/ioctl-tester - Add ioctl-tester
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0da759f1a36d
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 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 19:28 [BlueZ PATCH v2] tools/ioctl-tester - Add ioctl-tester Tedd Ho-Jeong An
2022-09-21 20:24 ` [BlueZ,v2] " bluez.test.bot
2022-09-22 1: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=166380902210.22214.8719483951038733963.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 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.