Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<intel-gfx-trybot@lists.freedesktop.org>,
	<jani.saarinen@intel.com>, <suresh.kumar.kurmi@intel.com>,
	<mohammed.thasleem@intel.com>
Subject: Re: [CI v2 0/2] acpi: pm: s2idle: LPS0 changes
Date: Mon, 12 Jan 2026 16:59:26 -0500	[thread overview]
Message-ID: <aWVuvvOVWUb1_xJO@intel.com> (raw)
In-Reply-To: <20260110154405.2825339-1-michal.grzelak@intel.com>

On Sat, Jan 10, 2026 at 04:44:03PM +0100, Michał Grzelak wrote:
> These series is a continuation of [1] and tests Rafael's changes.
> 
> [1] https://lore.kernel.org/intel-xe/20260109223442.2622647-1-michal.grzelak@intel.com/

https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7035

Thanks for the patches and diligence here.
Let's try to remove the first patch with a rebase next week and keep monitoring
the evolution on the second patch, as well as work to get a proper FW fix...

> 
> 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
> 

      parent reply	other threads:[~2026-01-12 21:59 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 ` [CI v2 0/2] " Michał Grzelak
2026-01-12 21:59 ` Rodrigo Vivi [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=aWVuvvOVWUb1_xJO@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx-trybot@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=michal.grzelak@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