From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/5] drm/i915/opregion: fixes and cleanups
Date: Thu, 13 Jan 2022 13:18:02 +0200 [thread overview]
Message-ID: <cover.1642072583.git.jani.nikula@intel.com> (raw)
Fix the UBSAN reported bit shift out of bounds first, as it's stable
backport material. Clean some stuff up after that.
Jani Nikula (5):
drm/i915/opregion: check port number bounds for SWSCI display power
state
drm/i915/opregion: abstract the check for valid swsci function
drm/i915/opregion: early exit from encoder notify if SWSCI isn't there
drm/i915/opregion: handle SWSCI Mailbox #2 obsoletion
drm/i915/opregion: debug log about Mailbox #2 for backlight
drivers/gpu/drm/i915/display/intel_opregion.c | 78 +++++++++++++++----
1 file changed, 62 insertions(+), 16 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-13 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 11:18 Jani Nikula [this message]
2022-01-13 11:18 ` [Intel-gfx] [PATCH 1/5] drm/i915/opregion: check port number bounds for SWSCI display power state Jani Nikula
2022-01-13 16:42 ` Lucas De Marchi
2022-01-13 16:53 ` Jani Nikula
2022-01-13 11:18 ` [Intel-gfx] [PATCH 2/5] drm/i915/opregion: abstract the check for valid swsci function Jani Nikula
2022-01-13 11:18 ` [Intel-gfx] [PATCH 3/5] drm/i915/opregion: early exit from encoder notify if SWSCI isn't there Jani Nikula
2022-01-13 11:18 ` [Intel-gfx] [PATCH 4/5] drm/i915/opregion: handle SWSCI Mailbox #2 obsoletion Jani Nikula
2022-01-13 11:18 ` [Intel-gfx] [PATCH 5/5] drm/i915/opregion: debug log about Mailbox #2 for backlight Jani Nikula
2022-01-13 12:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/opregion: fixes and cleanups Patchwork
2022-01-13 12:47 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=cover.1642072583.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.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