From: Stephen J. Fuhry <fuhrysteve@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>,
"Animesh Manna" <animesh.manna@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] drm/i915/display: fix ALPM error handling in psr_alpm_check()
Date: Thu, 11 Jun 2026 08:45:16 -0700 (PDT) [thread overview]
Message-ID: <6a2ad80c.dc7b3156.376f02.dea5@mx.google.com> (raw)
In-Reply-To: <20260611144956.710911-1-fuhrysteve@gmail.com>
Thanks for the explanation Jouni. I missed the has_psr guard in
intel_alpm_enable_lobf() -- LOBF can't be active while PSR2 is running,
so the double-read consequence is benign.
Dropping this patch.
next prev parent reply other threads:[~2026-06-12 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 12:54 [PATCH] drm/i915/display: guard intel_alpm_get_error() against non-ALPM sinks Stephen J. Fuhry
2026-06-11 13:17 ` Hogander, Jouni
2026-06-11 14:49 ` [PATCH] drm/i915/display: fix ALPM error handling in psr_alpm_check() Stephen J. Fuhry
2026-06-11 14:59 ` Hogander, Jouni
2026-06-11 15:45 ` Stephen J. Fuhry [this message]
2026-06-12 13:22 ` ✗ LGCI.VerificationFailed: failure for drm/i915/display: guard intel_alpm_get_error() against non-ALPM sinks (rev2) Patchwork
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=6a2ad80c.dc7b3156.376f02.dea5@mx.google.com \
--to=fuhrysteve@gmail.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jouni.hogander@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