All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com, kiran.k@intel.com
Subject: Re: [PATCH v2 2/3] Bluetooth: btintel_pcie: add MDBGC multi-buffer DBGC allocation
Date: Fri, 04 Sep 2026 17:50:05 +0000	[thread overview]
Message-ID: <178854420566.463198.14005383653530534379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904002939.622659-2-chandrashekar.devegowda@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,  4 Sep 2026 05:59:37 +0530 you wrote:
> Newer Intel BT PCIe variants (Nova Lake SCP2 and PTL FMP2) require
> three independent DRAM debug (DBGC) buffer pools instead of the
> single pool used by existing controllers.
> 
> Factor the per-pool buffer allocation into a common helper and add
> a multi-DBGC (MDBGC) setup path that allocates three pools using
> the fragment context format. MDBGC is used when the device reports
> an MDBGC-capable variant; otherwise the existing single-pool DBGC
> path is retained.
> 
> [...]

Here is the summary with links:
  - [v2,2/3] Bluetooth: btintel_pcie: add MDBGC multi-buffer DBGC allocation
    https://git.kernel.org/bluetooth/bluetooth-next/c/61f725843b50

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



  reply	other threads:[~2026-09-04 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 14:27 [PATCH v1 1/4] Bluetooth: btintel_pcie: remove duplicate BTINTEL_PCIE_MAGIC_NUM definition Chandrashekar Devegowda
2026-08-28 14:27 ` [PATCH v1 2/4] Bluetooth: btintel_pcie: add MDBGC multi-buffer DBGC allocation Chandrashekar Devegowda
2026-08-28 14:27 ` [PATCH v1 3/4] Bluetooth: btintel_pcie: log mailbox handler latency in msix_gp1_handler Chandrashekar Devegowda
2026-08-28 14:27 ` [PATCH v1 4/4] Bluetooth: btintel_pcie: unified decoder coredump format Chandrashekar Devegowda
2026-08-28 22:15 ` [v1,1/4] Bluetooth: btintel_pcie: remove duplicate BTINTEL_PCIE_MAGIC_NUM definition bluez.test.bot
2026-09-04  0:29 ` [PATCH v2 1/3] " Chandrashekar Devegowda
2026-09-04  1:10   ` [v2,1/3] " bluez.test.bot
2026-09-04 16:56   ` [PATCH v2 1/3] " patchwork-bot+bluetooth
2026-09-04  0:29 ` [PATCH v2 2/3] Bluetooth: btintel_pcie: add MDBGC multi-buffer DBGC allocation Chandrashekar Devegowda
2026-09-04 17:50   ` patchwork-bot+bluetooth [this message]
2026-09-04  0:29 ` [PATCH v2 3/3] Bluetooth: btintel_pcie: unified decoder coredump format Chandrashekar Devegowda
2026-09-04  0:46   ` [v2,3/3] " bluez.test.bot
2026-09-04  9:49   ` [PATCH v2 3/3] " Paul Menzel
2026-09-04 17:50   ` patchwork-bot+bluetooth
2026-09-04 16:56 ` [PATCH v1 1/4] Bluetooth: btintel_pcie: remove duplicate BTINTEL_PCIE_MAGIC_NUM definition patchwork-bot+bluetooth

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=178854420566.463198.14005383653530534379.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 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.