Linux bluetooth development
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe()
Date: Tue, 30 Jun 2026 20:32:37 +0000	[thread overview]
Message-ID: <178285155788.267316.541382714111705819.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630165919.102803-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 Tue, 30 Jun 2026 22:29:19 +0530 you wrote:
> The FLR branch in btintel_pcie_reset_work() open-coded the entire
> re-init sequence: btintel_pcie_release_hdev() (hci_unregister_dev +
> hci_free_dev), pci_try_reset_function(), enable_interrupts /
> config_msix / enable_bt / reset_ia / start_rx, then
> btintel_pcie_setup_hdev() (hci_alloc_dev_priv + hci_register_dev).
> Every probe() init step had to be kept in sync with this second
> copy in the reset path, and any failure mid-sequence left state to
> unwind by hand.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe()
    https://git.kernel.org/bluetooth/bluetooth-next/c/603b91aeb20a

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



      parent reply	other threads:[~2026-06-30 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 16:59 [PATCH v2] Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe() Kiran K
2026-06-30 18:35 ` [v2] " bluez.test.bot
2026-06-30 20:32 ` 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=178285155788.267316.541382714111705819.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 \
    /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