mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 glitches seen in dual A2DP streaming
Date: Thu, 23 Jan 2025 18:30:38 +0000	[thread overview]
Message-ID: <173765703824.1459736.8087924343892066142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250120141946.2690063-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 Mon, 20 Jan 2025 19:49:46 +0530 you wrote:
> This fixes a regression caused by previous commit for fixing truncated
> ACL data, which is causing some intermittent glitches when running two
> A2DP streams.
> 
> serdev_device_write_buf() is the root cause of the glitch, which is
> reverted, and the TX work will continue to write until the queue is empty.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming
    https://git.kernel.org/bluetooth/bluetooth-next/c/52f17be9931e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-01-23 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 14:19 Neeraj Sanjay Kale
2025-01-23 18:30 ` 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=173765703824.1459736.8087924343892066142.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
all inboxes | Powered by JetHome®