All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Lebedev <lsa.uz@pm.me>
To: Ravindra <ravindra@intel.com>
Cc: Kiran K <kiran.k@intel.com>,
	Chethan Tumkur Narayan <chethan.tumkur.narayan@intel.com>,
	Ravishankar Srivatsa <ravishankar.srivatsa@intel.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4
Date: Wed, 09 Sep 2026 12:36:39 +0000	[thread overview]
Message-ID: <20260909123633.72077-1-lsa.uz@pm.me> (raw)

For anyone arriving here later: this patch is now 2/2 of a two-patch series,
posted today with Ravindra's agreement.

  https://lore.kernel.org/linux-bluetooth/20260909123416.71919-1-lsa.uz@pm.me/

It is rebased onto bluetooth-next on top of Vladimir Kondratyev's fix, as
agreed. The rebase touched context only: the header hunk removes u8
pm_sx_event, and bluetooth-next has since gained struct btintel_pcie_mdbgc
mdbgc between dbgc and dmp_hdr, so the three-line context no longer matched.
The resulting diffstat is identical to this posting - 44 insertions, 22
deletions - and no reference to pm_sx_event is left in drivers/bluetooth.

Authorship, the Fixes: tag and the Assisted-by are unchanged; my Signed-off-by
sits beneath Ravindra's as the person passing it on.

Please treat this posting as superseded by the series.

Sergey


             reply	other threads:[~2026-09-09 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 12:36 Sergey Lebedev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-02  9:10 [PATCH v2] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4 Sergey Lebedev
2026-09-02 13:38 ` Sergey Lebedev
2026-09-08  9:32 ` Ravindra
2026-09-08 10:28   ` Sergey Lebedev
2026-09-02  4:28 Ravindra
2026-09-02  7:01 ` Paul Menzel

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=20260909123633.72077-1-lsa.uz@pm.me \
    --to=lsa.uz@pm.me \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravindra@intel.com \
    --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.