From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915/mchbar: move intel_mchbar_regs.h under include/drm/intel
Date: Tue, 7 Apr 2026 23:39:22 +0300 [thread overview]
Message-ID: <adVrejqcKCvIZSnj@intel.com> (raw)
In-Reply-To: <62ecb5604db457e1023ec58c5656239c46816417@intel.com>
On Tue, Apr 07, 2026 at 10:39:05PM +0300, Jani Nikula wrote:
> On Tue, 07 Apr 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Tue, Apr 07, 2026 at 01:57:41PM +0300, Jani Nikula wrote:
> >> drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c | 2 +-
> >> drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c | 2 +-
> >> drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
> >> drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 2 +-
> >
> > Those four don't seem to need the header anymore.
>
> The last one does need it after all. Sent v2 with the cleanup patches.
Ah, gvt. I probably wasn't even building that when I checked this :P
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-04-07 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:57 [PATCH 0/3] drm/i915: relocate mchbar and pci regs headers Jani Nikula
2026-04-07 10:57 ` [PATCH 1/3] drm/i915/mchbar: include intel_mchbar_regs.h from intel_mchbar.h Jani Nikula
2026-04-07 10:57 ` [PATCH 2/3] drm/i915/mchbar: move intel_mchbar_regs.h under include/drm/intel Jani Nikula
2026-04-07 16:10 ` Ville Syrjälä
2026-04-07 19:39 ` Jani Nikula
2026-04-07 20:39 ` Ville Syrjälä [this message]
2026-04-07 10:57 ` [PATCH 3/3] drm/i915/pci: move intel_pci_config.h " Jani Nikula
2026-04-07 16:01 ` Ville Syrjälä
2026-04-07 11:34 ` ✗ CI.checkpatch: warning for drm/i915: relocate mchbar and pci regs headers Patchwork
2026-04-07 11:35 ` ✓ CI.KUnit: success " Patchwork
2026-04-07 12:10 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-07 13:18 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-07 16:12 ` [PATCH 0/3] " Ville Syrjälä
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=adVrejqcKCvIZSnj@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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