From: "Michał Grzelak" <michal.grzelak@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@intel.com>,
intel-gfx-trybot@lists.freedesktop.org,
"Jani Saarinen" <jani.saarinen@intel.com>,
"Suresh Kumar Kurmi" <suresh.kumar.kurmi@intel.com>,
"Mohammed Thasleem" <mohammed.thasleem@intel.com>,
"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [CI v2 0/2] acpi: pm: s2idle: LPS0 changes
Date: Mon, 12 Jan 2026 18:05:21 +0100 (CET) [thread overview]
Message-ID: <4152311d-4f8c-d072-e072-326c0c1297db@intel.com> (raw)
In-Reply-To: <20260110154405.2825339-1-michal.grzelak@intel.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Sat, 10 Jan 2026, Michał Grzelak wrote:
> These series is a continuation of [1] and tests Rafael's changes.
Haven't included SoB: tag in each of bounced patches. Corrected
the mistake by replying to each patch with my SoB:.
>
> [1] https://lore.kernel.org/intel-xe/20260109223442.2622647-1-michal.grzelak@intel.com/
>
> BR,
> Michał
>
> Rafael J. Wysocki (2):
> ACPI: PM: s2idle: Add missing checks to acpi_s2idle_begin_lps0()
> ACPI: PM: s2idle: Add module parameter for LPS0 constraints checking
>
> drivers/acpi/x86/s2idle.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2026-01-12 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 15:44 [CI v2 0/2] acpi: pm: s2idle: LPS0 changes Michał Grzelak
2026-01-10 15:44 ` [CI v2 1/2] ACPI: PM: s2idle: Add missing checks to acpi_s2idle_begin_lps0() Michał Grzelak
2026-01-12 16:50 ` Michał Grzelak
2026-01-10 15:44 ` [CI v2 2/2] ACPI: PM: s2idle: Add module parameter for LPS0 constraints checking Michał Grzelak
2026-01-12 16:52 ` Michał Grzelak
2026-01-10 15:53 ` ✓ CI.KUnit: success for acpi: pm: s2idle: LPS0 changes Patchwork
2026-01-10 16:27 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-10 17:23 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-12 17:05 ` Michał Grzelak [this message]
2026-01-12 21:59 ` [CI v2 0/2] " Rodrigo Vivi
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=4152311d-4f8c-d072-e072-326c0c1297db@intel.com \
--to=michal.grzelak@intel.com \
--cc=intel-gfx-trybot@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jani.saarinen@intel.com \
--cc=mohammed.thasleem@intel.com \
--cc=suresh.kumar.kurmi@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