Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH 0/3] drm/xe: Cleanup xe_mmio.h
Date: Mon, 20 May 2024 20:18:11 +0200	[thread overview]
Message-ID: <20240520181814.2392-1-michal.wajdeczko@intel.com> (raw)

Unfortunately, this is cross i915/Xe series.

Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>

Michal Wajdeczko (3):
  drm/i915/display: Add missing include to intel_vga.c
  drm/xe: Don't rely on indirect includes from xe_mmio.h
  drm/xe: Cleanup xe_mmio.h

 drivers/gpu/drm/i915/display/intel_vga.c | 1 +
 drivers/gpu/drm/xe/xe_device.c           | 2 ++
 drivers/gpu/drm/xe/xe_gsc.c              | 2 ++
 drivers/gpu/drm/xe/xe_gt_ccs_mode.c      | 1 +
 drivers/gpu/drm/xe/xe_guc_ads.c          | 1 +
 drivers/gpu/drm/xe/xe_huc.c              | 2 ++
 drivers/gpu/drm/xe/xe_mmio.c             | 7 +++++--
 drivers/gpu/drm/xe/xe_mmio.h             | 9 +--------
 drivers/gpu/drm/xe/xe_mocs.c             | 1 +
 drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c   | 1 +
 drivers/gpu/drm/xe/xe_uc_fw.c            | 1 +
 11 files changed, 18 insertions(+), 10 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-05-20 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 18:18 Michal Wajdeczko [this message]
2024-05-20 18:18 ` [PATCH 1/3] drm/i915/display: Add missing include to intel_vga.c Michal Wajdeczko
2024-05-21  9:24   ` Jani Nikula
2024-05-20 18:18 ` [PATCH 2/3] drm/xe: Don't rely on indirect includes from xe_mmio.h Michal Wajdeczko
2024-05-21 14:01   ` Francois Dugast
2024-05-21 14:10     ` Michal Wajdeczko
2024-05-21 14:50       ` Francois Dugast
2024-05-20 18:18 ` [PATCH 3/3] drm/xe: Cleanup xe_mmio.h Michal Wajdeczko
2024-05-22  9:39   ` Ghimiray, Himal Prasad
2024-05-20 18:23 ` ✓ CI.Patch_applied: success for " Patchwork
2024-05-20 18:23 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-20 18:24 ` ✓ CI.KUnit: success " Patchwork
2024-05-20 18:36 ` ✓ CI.Build: " Patchwork
2024-05-20 18:39 ` ✓ CI.Hooks: " Patchwork
2024-05-20 18:40 ` ✗ CI.checksparse: warning " Patchwork
2024-05-20 19:02 ` ✓ CI.BAT: success " Patchwork
2024-05-20 20:00 ` ✓ CI.FULL: " 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=20240520181814.2392-1-michal.wajdeczko@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lucas.demarchi@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