public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, Lucas De Marchi <lucas.demarchi@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [Intel-gfx] [PATCH 0/4] drm/i915: further device info cleanups
Date: Thu,  8 Jun 2023 18:09:01 +0300	[thread overview]
Message-ID: <cover.1686236840.git.jani.nikula@intel.com> (raw)

Building on Matt's display info separation, we can finally trivially
make device info a const pointer to rodata.

BR,
Jani.

Cc: Matt Roper <matthew.d.roper@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>


Jani Nikula (4):
  drm/i915: separate display info printing from the rest
  drm/i915: fix display info usage
  drm/i915: move display device and runtime info to struct intel_display
  drm/i915: make device info a const pointer to rodata

 drivers/gpu/drm/i915/display/intel_display.h  |  2 +-
 .../gpu/drm/i915/display/intel_display_core.h |  9 ++++
 .../drm/i915/display/intel_display_device.c   | 21 ++++++++++
 .../drm/i915/display/intel_display_device.h   |  5 +++
 drivers/gpu/drm/i915/i915_debugfs.c           |  1 +
 drivers/gpu/drm/i915/i915_driver.c            |  2 +
 drivers/gpu/drm/i915/i915_drv.h               |  9 ++--
 drivers/gpu/drm/i915/i915_gpu_error.c         |  6 +++
 drivers/gpu/drm/i915/i915_gpu_error.h         |  3 ++
 drivers/gpu/drm/i915/intel_device_info.c      | 42 +++----------------
 drivers/gpu/drm/i915/intel_device_info.h      |  4 --
 11 files changed, 58 insertions(+), 46 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-06-08 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 15:09 Jani Nikula [this message]
2023-06-08 15:09 ` [Intel-gfx] [PATCH 1/4] drm/i915: separate display info printing from the rest Jani Nikula
2023-06-08 21:52   ` Matt Roper
2023-06-08 15:09 ` [Intel-gfx] [PATCH 2/4] drm/i915: fix display info usage Jani Nikula
2023-06-08 21:53   ` Matt Roper
2023-06-08 15:09 ` [Intel-gfx] [PATCH 3/4] drm/i915: move display device and runtime info to struct intel_display Jani Nikula
2023-06-08 22:04   ` Matt Roper
2023-06-08 15:09 ` [Intel-gfx] [PATCH 4/4] drm/i915: make device info a const pointer to rodata Jani Nikula
2023-06-08 22:09   ` Matt Roper
2023-06-08 19:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: further device info cleanups Patchwork
2023-06-08 19:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-08 19:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-10  2:35 ` [Intel-gfx] ✗ Fi.CI.IGT: 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.1686236840.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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