From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com, vijay.satija@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: Add additional to checks to clear TX/RX paths
Date: Thu, 24 Apr 2025 14:10:29 +0000 [thread overview]
Message-ID: <174550382975.3366851.2565866147493840939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250420015156.192605-1-kiran.k@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 20 Apr 2025 07:21:56 +0530 you wrote:
> Due to a hardware issue, there is a possibility that the driver may miss
> an MSIx interrupt on the RX/TX data path. Since the TX and RX paths are
> independent, when a TX MSIx interrupt occurs, the driver can check the
> RX queue for any pending data and process it if present. The same
> approach applies to the RX path.
>
> Signed-off-by: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
> Signed-off-by: Kiran K <kiran.k@intel.com>
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel_pcie: Add additional to checks to clear TX/RX paths
https://git.kernel.org/bluetooth/bluetooth-next/c/ac1f44f12090
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-04-24 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 1:51 [PATCH v1] Bluetooth: btintel_pcie: Add additional to checks to clear TX/RX paths Kiran K
2025-04-20 3:16 ` [v1] " bluez.test.bot
2025-04-24 14: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=174550382975.3366851.2565866147493840939.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.com \
--cc=vijay.satija@intel.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