[Intel-gfx] [PATCH 2/3] drm/i915: fix intel_fb_obj_flush documentation

Rodrigo Vivi rodrigo.vivi at gmail.com
Thu Jul 9 10:00:57 PDT 2015


ops... Sorry..
I could swear I had added this... or probably forgot to send the version
that had it...

Anyway:

Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>


On Wed, Jul 8, 2015 at 2:09 PM Paulo Zanoni <przanoni at gmail.com> wrote:

> From: Paulo Zanoni <paulo.r.zanoni at intel.com>
>
> Reported by the kbuild test robot.
>
> Regression introduced by:
> commit de152b627eb3018de91ec5c5a50b38e17d80a88b
> Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
> Date:   Tue Jul 7 16:28:51 2015 -0700
>     drm/i915: Add origin to frontbuffer tracking flush
>
> (I reviewed this commit, so it's also my fault)
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni at intel.com>
> ---
>  drivers/gpu/drm/i915/intel_frontbuffer.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_frontbuffer.c
> b/drivers/gpu/drm/i915/intel_frontbuffer.c
> index 122533d..dc8f14d 100644
> --- a/drivers/gpu/drm/i915/intel_frontbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_frontbuffer.c
> @@ -136,6 +136,7 @@ static void intel_frontbuffer_flush(struct drm_device
> *dev,
>   * intel_fb_obj_flush - flush frontbuffer object
>   * @obj: GEM object to flush
>   * @retire: set when retiring asynchronous rendering
> + * @origin: which operation caused the flush
>   *
>   * This function gets called every time rendering on the given object has
>   * completed and frontbuffer caching can be started again. If @retire is
> true
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20150709/7b7a7248/attachment-0001.html>


More information about the Intel-gfx mailing list