From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
willemdebruijn.kernel@gmail.com, kerneljasonxing@gmail.com
Subject: Re: [PATCH] Bluetooth: increment TX timestamping tskey always for stream sockets
Date: Thu, 03 Apr 2025 20:20:34 +0000 [thread overview]
Message-ID: <174371163427.2672071.7073463393326839454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cf8e3a5bd2f4dbdba54d785d744e2b1970b28301.1743699406.git.pav@iki.fi>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 3 Apr 2025 19:57:59 +0300 you wrote:
> Documentation/networking/timestamping.rst implies TX timestamping OPT_ID
> tskey increments for each sendmsg. In practice: TCP socket increments
> it for all sendmsg, timestamping on or off, but UDP only when
> timestamping is on. The user-visible counter resets when OPT_ID is
> turned on, so difference can be seen only if timestamping is enabled for
> some packets only (eg. via SO_TIMESTAMPING CMSG).
>
> [...]
Here is the summary with links:
- Bluetooth: increment TX timestamping tskey always for stream sockets
https://git.kernel.org/bluetooth/bluetooth-next/c/2c1cf148c1fa
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-03 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 16:57 [PATCH] Bluetooth: increment TX timestamping tskey always for stream sockets Pauli Virtanen
2025-04-03 19:04 ` bluez.test.bot
2025-04-03 20: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=174371163427.2672071.7073463393326839454.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pav@iki.fi \
--cc=willemdebruijn.kernel@gmail.com \
/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