All of lore.kernel.org
 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 v1] Bluetooth: btintel_pcie: split coredump worker into per-trigger works
Date: Wed, 08 Jul 2026 16:10:04 +0000	[thread overview]
Message-ID: <178352700464.3009771.15016263615696178190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702170359.26233-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 Thu,  2 Jul 2026 22:33:59 +0530 you wrote:
> btintel_pcie_coredump_worker() handled three unrelated jobs in one
> work item: collect a DRAM trace coredump, read the hardware exception
> event, and read the firmware-trigger event. The worker walked three
> flag bits at runtime and each interrupt path mutated multiple bits
> to communicate which sub-jobs the worker should run, which made the
> ownership rules for those bits hard to reason about and entangled
> the trigger reason with the in-progress accounting.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btintel_pcie: split coredump worker into per-trigger works
    https://git.kernel.org/bluetooth/bluetooth-next/c/ca75417ab179

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-07-08 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 17:03 [PATCH v1] Bluetooth: btintel_pcie: split coredump worker into per-trigger works Kiran K
2026-07-02 18:48 ` [v1] " bluez.test.bot
2026-07-08 16: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=178352700464.3009771.15016263615696178190.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.