From: Jani Nikula <jani.nikula@intel.com>
To: Luca Coelho <luca@coelho.fi>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [RESEND 6/6] drm/i915/display: drop i915_drv.h include from intel_display_trace.h
Date: Mon, 16 Dec 2024 18:45:35 +0200 [thread overview]
Message-ID: <877c7zshjk.fsf@intel.com> (raw)
In-Reply-To: <8c64a63a532c35c7b16e3238f19c8e02eb8c4685.camel@coelho.fi>
On Fri, 13 Dec 2024, Luca Coelho <luca@coelho.fi> wrote:
> On Wed, 2024-11-20 at 14:03 +0200, Jani Nikula wrote:
>> Finish the job of removing implicit dependencies on i915_drv.h via other
>> includes in display code. Add a few missing explicit includes.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>
> Done! Overall a nice series. :)
>
>
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>
Thanks, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-16 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 12:03 [RESEND 0/6] drm/i915/display: make all i915_drv.h includes explicit Jani Nikula
2024-11-20 12:03 ` [RESEND 1/6] drm/i915/gvt: always pass struct intel_display * to register macros Jani Nikula
2024-12-13 8:57 ` Luca Coelho
2024-11-20 12:03 ` [RESEND 2/6] drm/i915: extract intel_uncore_trace.[ch] Jani Nikula
2024-12-13 9:04 ` Luca Coelho
2024-11-20 12:03 ` [RESEND 3/6] drm/i915/display: add intel_display_conversion.c to hide stuff better Jani Nikula
2024-12-13 9:06 ` Luca Coelho
2024-11-20 12:03 ` [RESEND 4/6] drm/i915/uncore: add to_intel_uncore() and use it Jani Nikula
2024-12-13 10:07 ` Luca Coelho
2024-11-20 12:03 ` [RESEND 5/6] drm/i915/display: add struct drm_device to struct intel_display conversion function Jani Nikula
2024-12-13 10:18 ` Luca Coelho
2024-11-20 12:03 ` [RESEND 6/6] drm/i915/display: drop i915_drv.h include from intel_display_trace.h Jani Nikula
2024-12-13 10:20 ` Luca Coelho
2024-12-16 16:45 ` Jani Nikula [this message]
2024-11-20 12:24 ` ✓ CI.Patch_applied: success for drm/i915/display: make all i915_drv.h includes explicit (rev2) Patchwork
2024-11-20 12:24 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-20 12:26 ` ✓ CI.KUnit: success " Patchwork
2024-11-20 12:44 ` ✓ CI.Build: " Patchwork
2024-11-20 12:46 ` ✓ CI.Hooks: " Patchwork
2024-11-20 12:47 ` ✗ CI.checksparse: warning " Patchwork
2024-11-20 13:07 ` ✓ CI.BAT: success " Patchwork
2024-11-20 13:12 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-11-20 13:12 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-20 13:25 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-20 22:12 ` ✗ Xe.CI.Full: 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=877c7zshjk.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luca@coelho.fi \
/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.