diff options
| author | Pauli Virtanen <[email protected]> | 2025-04-03 16:57:59 +0000 |
|---|---|---|
| committer | Luiz Augusto von Dentz <[email protected]> | 2025-04-10 17:09:25 +0000 |
| commit | c174cd0945ad3f1b7e48781e0d22b94f9e89b28b (patch) | |
| tree | 1fced9d6d30d9e5f3ae9e612cc099b86cc911cf8 /drivers/fpga/tests/fpga-bridge-test.c | |
| parent | Bluetooth: qca: fix NV variant for one of WCN3950 SoCs (diff) | |
| download | kernel-c174cd0945ad3f1b7e48781e0d22b94f9e89b28b.tar.gz kernel-c174cd0945ad3f1b7e48781e0d22b94f9e89b28b.zip | |
Bluetooth: increment TX timestamping tskey always for stream sockets
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).
Fix BT sockets to work in the same way: stream sockets increment tskey
for all sendmsg (seqpacket already increment for timestamped only).
Fixes: 134f4b39df7b ("Bluetooth: add support for skb TX SND/COMPLETION timestamping")
Signed-off-by: Pauli Virtanen <[email protected]>
Signed-off-by: Luiz Augusto von Dentz <[email protected]>
Diffstat (limited to 'drivers/fpga/tests/fpga-bridge-test.c')
0 files changed, 0 insertions, 0 deletions