From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] hciemu: Fix silently dropping packet if writev return -EAGAIN
Date: Tue, 03 Mar 2026 15:40:06 +0000 [thread overview]
Message-ID: <177255240654.1348433.4748395920578414611.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260226200330.313530-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 26 Feb 2026 15:03:29 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The code has been silently dropping packets due to lack of buffer
> since hciemu design is single threaded it cannot do partial writes
> or flushes to force the buffer to be consumed and give space to the
> next chunk, so in order to fix this the code will now attempt to
> detect if a socket runs out of space and automatically bump the
> buffer with use of SO_SNDBUF.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] hciemu: Fix silently dropping packet if writev return -EAGAIN
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=744fad3c342e
- [BlueZ,v2,2/2] bthost: Add segmentation support for L2CAP LE-(E)CRED mode
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b138a0849ba2
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:[~2026-03-03 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 20:03 [PATCH BlueZ v2 1/2] hciemu: Fix silently dropping packet if writev return -EAGAIN Luiz Augusto von Dentz
2026-02-26 20:03 ` [PATCH BlueZ v2 2/2] bthost: Add segmentation support for L2CAP LE-(E)CRED mode Luiz Augusto von Dentz
2026-02-26 21:05 ` [BlueZ,v2,1/2] hciemu: Fix silently dropping packet if writev return -EAGAIN bluez.test.bot
2026-03-03 15:40 ` 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=177255240654.1348433.4748395920578414611.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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