From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/3] shared/io: add watcher to be used with TX timestamping
Date: Wed, 09 Apr 2025 14:20:43 +0000 [thread overview]
Message-ID: <174420844315.2837833.13343345953883708543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aa9cdb0ec03c5fcbf12a2df3d183c47de664bdc1.1744144760.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, 8 Apr 2025 23:42:38 +0300 you wrote:
> Add special implementation of fd watcher GSource for audio use.
>
> For audio use cases, sound server may turn on TX timestamping on a
> socket that we are watching. In this case, we shall not consider the TX
> timestamping POLLERR as a socket error condition, nor read the TX
> timestamps.
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] shared/io: add watcher to be used with TX timestamping
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b19d445b0192
- [BlueZ,2/3] avdtp: don't consider TX timestamps as errors
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0e831d8e6709
- [BlueZ,3/3] bap: don't consider TX timestamps as errors
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9f167d495adb
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-04-09 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:42 [PATCH BlueZ 1/3] shared/io: add watcher to be used with TX timestamping Pauli Virtanen
2025-04-08 20:42 ` [PATCH BlueZ 2/3] avdtp: don't consider TX timestamps as errors Pauli Virtanen
2025-04-08 20:42 ` [PATCH BlueZ 3/3] bap: " Pauli Virtanen
2025-04-08 22:31 ` [BlueZ,1/3] shared/io: add watcher to be used with TX timestamping bluez.test.bot
2025-04-09 14:20 ` 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=174420844315.2837833.13343345953883708543.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.