mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Lebedev <lsa.uz@pm.me>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 7.3 0000/2651] 7.3.6-rc1 review
Date: Thu, 19 Nov 2026 03:26:02 +0000	[thread overview]
Message-ID: <20261119032558.37385-1-lsa.uz@pm.me> (raw)

Built with Ubuntu's config (Rust off) and booted on a Surface Pro 11
(Lunar Lake, Intel BE201 Bluetooth over btintel_pcie). Ten s2idle
cycles: no suspend failures, no alive-interrupt timeouts, and Bluetooth
up and scanning after each resume. That covers the btintel_pcie series
(1882-1886); its PM paths are the same as in v7.4-rc1.

One problem, reported separately: 1120/2651 (debugfs_create_str()
read-only) is queued without the two patches before it, and warns at
boot here.

Tested-by: Sergey Lebedev <lsa.uz@pm.me> # Surface Pro 11, btintel_pcie s2idle


             reply	other threads:[~2026-11-19  3:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  3:26 Sergey Lebedev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-18 14:20 Greg Kroah-Hartman
2026-11-18 16:59 ` Brett A C Sheffield
2026-11-18 17:17 ` Pavel Machek
2026-11-18 19:02 ` Thorsten Leemhuis
2026-11-18 20:39   ` Gary Guo
2026-11-19  3:23     ` Alice C. Munduruca
2026-11-18 19:08 ` Thorsten Leemhuis
2026-11-18 19:59 ` Florian Fainelli
2026-11-18 22:30 ` Takeshi Ogasawara
2026-11-19  3:32 ` Peter Schneider

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=20261119032558.37385-1-lsa.uz@pm.me \
    --to=lsa.uz@pm.me \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®