From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/3] tools/tester: test COMPLETION timestamps
Date: Tue, 18 Mar 2025 22:00:32 +0000 [thread overview]
Message-ID: <174233523203.475282.2860046994782971122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3d378acca803b578522100e8f9fd3d6adb1deb25.1742324646.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 Tue, 18 Mar 2025 21:07:08 +0200 you wrote:
> Add support for SOF_TIMESTAMPING_TX_COMPLETION also in cases where
> errqueue.h is old and doesn't define it.
>
> Support timestamps of different types arriving out of order, as multiple
> SND may well arrive before COMPLETION. Also allow TX timestamp arriving
> before bthost receives data, as that may well happen.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] tools/tester: test COMPLETION timestamps
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c89e18fa55e2
- [BlueZ,v2,2/3] l2cap-tester: add test for stream socket TX timestamping
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fe5a5f509e0c
- [BlueZ,v2,3/3] tools/tester: enable TX timestamping tests by default
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f4b6a649ccdd
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:[~2025-03-18 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 19:07 [PATCH BlueZ v2 1/3] tools/tester: test COMPLETION timestamps Pauli Virtanen
2025-03-18 19:07 ` [PATCH BlueZ v2 2/3] l2cap-tester: add test for stream socket TX timestamping Pauli Virtanen
2025-03-18 19:07 ` [PATCH BlueZ v2 3/3] tools/tester: enable TX timestamping tests by default Pauli Virtanen
2025-03-18 20:08 ` [BlueZ,v2,1/3] tools/tester: test COMPLETION timestamps bluez.test.bot
2025-03-18 22:00 ` 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=174233523203.475282.2860046994782971122.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.