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
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: Fix incorrect MAC access programming
Date: Fri, 15 May 2026 15:50:05 +0000 [thread overview]
Message-ID: <177886020563.52984.12391876062820489757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514190248.1275299-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 Fri, 15 May 2026 00:32:48 +0530 you wrote:
> btintel_pcie_get_mac_access() and btintel_pcie_release_mac_access()
> were programming STOP_MAC_ACCESS_DIS and XTAL_CLK_REQ in addition to
> the MAC_ACCESS_REQ handshake. These bits are not part of the host
> MAC-access handshake on the supported parts; the driver was
> programming them incorrectly. Drop the writes so the register update
> contains only the bits the controller actually consumes.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btintel_pcie: Fix incorrect MAC access programming
https://git.kernel.org/bluetooth/bluetooth-next/c/663fc68494ce
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-05-15 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 19:02 [PATCH v2] Bluetooth: btintel_pcie: Fix incorrect MAC access programming Kiran K
2026-05-14 20:35 ` [v2] " bluez.test.bot
2026-05-15 15:50 ` 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=177886020563.52984.12391876062820489757.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@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 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.