All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 0/8] drm/i915: drm_i915_private and xe_device cleanups
Date: Tue, 09 Apr 2024 11:43:10 +0300	[thread overview]
Message-ID: <87y19n7wpt.fsf@intel.com> (raw)
In-Reply-To: <umdjxcjjfmxpc52sai7d5ltgntcweilfd7e4n3pkvxvqhq23r4@5oaddgmh64mz>

On Mon, 08 Apr 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Tue, Apr 09, 2024 at 12:02:17AM +0300, Jani Nikula wrote:
>>On Mon, 08 Apr 2024, Jani Nikula <jani.nikula@intel.com> wrote:
>>> Continue cleaning up the members from drm_i915_private and xe_device to
>>> struct intel_display.
>>
>>Lucas, there's a bunch of xe changes included here, ack for merging via
>>drm-intel-next?
>
>
> Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> I skimmed through the series and left just one comment. It may be very
> well because I skimmed through it too fast though. I agree on merging
> it through drm-intel-next.

Thanks for the review and ack, pushed patches 1-7 to drm-intel-next. I
decided the renaming, if any, can come later.

There was a trivial conflict with patch 1, pushed it anyway, but skipped
patch 8 for now also due to conflicts, and it didn't apply to
drm-xe-next either. Need to sync up the branches first.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-09  8:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 18:08 [PATCH 0/8] drm/i915: drm_i915_private and xe_device cleanups Jani Nikula
2024-04-08 18:08 ` [PATCH 1/8] drm/i915/gt: drop display clock info from gt debugfs Jani Nikula
2024-04-08 18:08 ` [PATCH 2/8] drm/i915: move skl_preferred_vco_freq to display substruct Jani Nikula
2024-04-08 18:08 ` [PATCH 3/8] drm/i915: move max_dotclk_freq " Jani Nikula
2024-04-08 18:08 ` [PATCH 4/8] drm/i915: move vblank_enabled " Jani Nikula
2024-04-08 18:08 ` [PATCH 5/8] drm/i915: move display_irqs_enabled " Jani Nikula
2024-04-08 18:08 ` [PATCH 6/8] drm/i915: move de_irq_mask " Jani Nikula
2024-04-08 21:07   ` Lucas De Marchi
2024-04-08 18:08 ` [PATCH 7/8] drm/i915: move pipestat_irq_mask " Jani Nikula
2024-04-08 18:08 ` [PATCH 8/8] drm/xe/display: remove unused xe->enabled_irq_mask Jani Nikula
2024-04-08 18:15 ` [PATCH 0/8] drm/i915: drm_i915_private and xe_device cleanups Ville Syrjälä
2024-04-08 19:17 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-08 19:18 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-08 19:19 ` ✓ CI.KUnit: success " Patchwork
2024-04-08 19:31 ` ✓ CI.Build: " Patchwork
2024-04-08 19:36 ` ✓ CI.Hooks: " Patchwork
2024-04-08 19:38 ` ✗ CI.checksparse: warning " Patchwork
2024-04-08 20:02 ` ✓ CI.BAT: success " Patchwork
2024-04-08 21:02 ` [PATCH 0/8] " Jani Nikula
2024-04-08 21:10   ` Lucas De Marchi
2024-04-09  8:43     ` Jani Nikula [this message]
2024-04-08 22:31 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-04-08 22:31 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-08 22:36 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-09  1:41 ` ✗ CI.FULL: failure " Patchwork
2024-04-10  3:35 ` ✓ Fi.CI.IGT: success " 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=87y19n7wpt.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=ville.syrjala@linux.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 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.