From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Include i915_active header in frontbuffer tracking code
Date: Mon, 2 Oct 2023 05:45:25 +0000 [thread overview]
Message-ID: <163b92f98a6988704bd2396aa3c50959110ff075.camel@intel.com> (raw)
In-Reply-To: <87fs2xi5gi.fsf@intel.com>
On Fri, 2023-09-29 at 14:28 +0300, Jani Nikula wrote:
> On Fri, 29 Sep 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> > Intel frontbuffer tracking code is using i915_active functions ->
> > include
> > i915_active.h directly instead of relying getting indirectly
> > included.
> >
> > Cc: Jani Nikula <jani.nikula@intel.com>
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thank you Jani. This is now merged.
BR,
Jouni Högander
>
>
> > ---
> > drivers/gpu/drm/i915/display/intel_frontbuffer.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > index 412a19a888a2..ec46716b2f49 100644
> > --- a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > +++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > @@ -56,6 +56,7 @@
> > */
> >
> > #include "gem/i915_gem_object_frontbuffer.h"
> > +#include "i915_active.h"
> > #include "i915_drv.h"
> > #include "intel_display_trace.h"
> > #include "intel_display_types.h"
>
next prev parent reply other threads:[~2023-10-02 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:20 [Intel-gfx] [PATCH] drm/i915/display: Include i915_active header in frontbuffer tracking code Jouni Högander
2023-09-29 11:28 ` Jani Nikula
2023-10-02 5:45 ` Hogander, Jouni [this message]
2023-09-29 15:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-09-29 22:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=163b92f98a6988704bd2396aa3c50959110ff075.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@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