From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
ilpo.jarvinen@linux.intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, amitkumar.karwar@nxp.com,
sherry.sun@nxp.com, ziniu.wang_1@nxp.com
Subject: Re: [PATCH v1] Bluetooth: btnxpuart: Fix driver sending truncated data
Date: Wed, 08 Jan 2025 16:10:34 +0000 [thread overview]
Message-ID: <173635263453.697160.15946263371531689963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241220130252.1903536-1-neeraj.sanjaykale@nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 20 Dec 2024 18:32:52 +0530 you wrote:
> This fixes the apparent controller hang issue seen during stress test
> where the host sends a truncated payload, followed by HCI commands. The
> controller treats these HCI commands as a part of previously truncated
> payload, leading to command timeouts.
>
> Adding a serdev_device_wait_until_sent() call after
> serdev_device_write_buf() fixed the issue.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btnxpuart: Fix driver sending truncated data
https://git.kernel.org/bluetooth/bluetooth-next/c/fb966c19be55
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-01-08 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:02 [PATCH v1] Bluetooth: btnxpuart: Fix driver sending truncated data Neeraj Sanjay Kale
2025-01-08 16:10 ` 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=173635263453.697160.15946263371531689963.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=sherry.sun@nxp.com \
--cc=ziniu.wang_1@nxp.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