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/backlight: drop implict dev_priv etc.
Date: Mon, 5 Dec 2022 16:11:13 +0200 [thread overview]
Message-ID: <cover.1670249413.git.jani.nikula@intel.com> (raw)
Dump a local branch I've had laying around for a while.
Jani Nikula (5):
drm/i915/backlight: use VLV_DISPLAY_BASE for VLV/CHV backlight
registers
drm/i915/backlight: get rid of the implicit dev_priv
drm/i915/backlight: mass rename dev_priv to i915
drm/i915/backlight: drop drm_device local variables in favor of i915
drm/i915/backlight: convert DRM_DEBUG_KMS() to drm_dbg_kms()
.../gpu/drm/i915/display/intel_backlight.c | 539 +++++++++---------
.../drm/i915/display/intel_backlight_regs.h | 27 +-
2 files changed, 271 insertions(+), 295 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-05 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 14:11 Jani Nikula [this message]
2022-12-05 14:11 ` [Intel-gfx] [PATCH 1/5] drm/i915/backlight: use VLV_DISPLAY_BASE for VLV/CHV backlight registers Jani Nikula
2022-12-05 14:17 ` Jani Nikula
2022-12-05 17:25 ` Rodrigo Vivi
2022-12-07 9:36 ` Jani Nikula
2022-12-05 14:11 ` [Intel-gfx] [PATCH 2/5] drm/i915/backlight: get rid of the implicit dev_priv Jani Nikula
2022-12-05 14:11 ` [Intel-gfx] [PATCH 3/5] drm/i915/backlight: mass rename dev_priv to i915 Jani Nikula
2022-12-05 14:11 ` [Intel-gfx] [PATCH 4/5] drm/i915/backlight: drop drm_device local variables in favor of i915 Jani Nikula
2022-12-05 14:11 ` [Intel-gfx] [PATCH 5/5] drm/i915/backlight: convert DRM_DEBUG_KMS() to drm_dbg_kms() Jani Nikula
2022-12-05 15:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/backlight: drop implict dev_priv etc Patchwork
2022-12-05 15:58 ` [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.1670249413.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.