From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] bthost: Allow sending ISO packets with sequence number and timestamp
Date: Mon, 27 Feb 2023 21:40:18 +0000 [thread overview]
Message-ID: <167753401817.12319.155272368674120365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b071b484b1b199ad69412ca0b2610c9c75fe7181.1677361002.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 25 Feb 2023 21:42:50 +0000 you wrote:
> Change bthost_send_iso to take packet sequence number and timestamp, and
> allow it to send timestamped HCI ISO data packets.
>
> Currently, btdev passes through ISO packets, so this can also be used to
> test RX timestamping.
> ---
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] bthost: Allow sending ISO packets with sequence number and timestamp
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=80a45cb6a240
- [BlueZ,2/2] iso-tester: Add test for central receiving timestamped ISO packet
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2be849c2398b
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-02-27 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 21:42 [PATCH BlueZ 1/2] bthost: Allow sending ISO packets with sequence number and timestamp Pauli Virtanen
2023-02-25 21:42 ` [PATCH BlueZ 2/2] iso-tester: Add test for central receiving timestamped ISO packet Pauli Virtanen
2023-02-25 23:31 ` [BlueZ,1/2] bthost: Allow sending ISO packets with sequence number and timestamp bluez.test.bot
2023-02-27 21:40 ` 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=167753401817.12319.155272368674120365.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.