From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: copy RX timestamp to new fragments
Date: Thu, 24 Apr 2025 21:10:28 +0000 [thread overview]
Message-ID: <174552902850.3492605.4655894838579542250.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <01117138d56019a8598f24f0df2dd289713cfab4.1745524193.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, 24 Apr 2025 22:51:03 +0300 you wrote:
> Copy timestamp too when allocating new skb for received fragment.
> Fixes missing RX timestamps with fragmentation.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Pauli Virtanen <pav@iki.fi>
> ---
> net/bluetooth/l2cap_core.c | 3 +++
> 1 file changed, 3 insertions(+)
Here is the summary with links:
- Bluetooth: L2CAP: copy RX timestamp to new fragments
https://git.kernel.org/bluetooth/bluetooth-next/c/60b82ca5d6bc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-04-24 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 19:51 [PATCH] Bluetooth: L2CAP: copy RX timestamp to new fragments Pauli Virtanen
2025-04-24 20:19 ` Luiz Augusto von Dentz
2025-04-24 20:43 ` Pauli Virtanen
2025-04-24 20:35 ` bluez.test.bot
2025-04-24 21:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 18:59 [PATCH] " Pauli Virtanen
2025-04-24 19:10 ` Luiz Augusto von Dentz
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=174552902850.3492605.4655894838579542250.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.