public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: fix intel_frontbuffer_flip documentation
Date: Thu, 9 Jul 2015 19:18:18 +0200	[thread overview]
Message-ID: <20150709171818.GD7410@phenom.ffwll.local> (raw)
In-Reply-To: <1436389719-16392-3-git-send-email-przanoni@gmail.com>

On Wed, Jul 08, 2015 at 06:08:39PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> 
> Reported by the kbuild test robot.
> 
> Regression introduced by:
> commit fdbff9282c0f5f61ffc87d57461b04d943250910
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Thu Jun 18 11:23:24 2015 +0200
>     drm/i915: Clear fb_tracking.busy_bits also for synchronous flips
> 
> (I reviewed this commit, so it's also my fault)
> 
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>

Patch 1&3 also merged to dinq, thanks.
-Daniel

> ---
>  Documentation/DocBook/drm.tmpl           | 1 -
>  drivers/gpu/drm/i915/intel_frontbuffer.c | 1 -
>  2 files changed, 2 deletions(-)
> 
> diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
> index 596b11d..30b3651 100644
> --- a/Documentation/DocBook/drm.tmpl
> +++ b/Documentation/DocBook/drm.tmpl
> @@ -4012,7 +4012,6 @@ int num_ioctls;</synopsis>
>          <title>Frontbuffer Tracking</title>
>  !Pdrivers/gpu/drm/i915/intel_frontbuffer.c frontbuffer tracking
>  !Idrivers/gpu/drm/i915/intel_frontbuffer.c
> -!Fdrivers/gpu/drm/i915/intel_drv.h intel_frontbuffer_flip
>  !Fdrivers/gpu/drm/i915/i915_gem.c i915_gem_track_fb
>        </sect2>
>        <sect2>
> diff --git a/drivers/gpu/drm/i915/intel_frontbuffer.c b/drivers/gpu/drm/i915/intel_frontbuffer.c
> index dc8f14d..b5b1d25 100644
> --- a/drivers/gpu/drm/i915/intel_frontbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_frontbuffer.c
> @@ -229,7 +229,6 @@ void intel_frontbuffer_flip_complete(struct drm_device *dev,
>   *
>   * Can be called without any locks held.
>   */
> -
>  void intel_frontbuffer_flip(struct drm_device *dev,
>  			    unsigned frontbuffer_bits)
>  {
> -- 
> 2.1.4
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-07-09 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 21:08 [PATCH 1/3] drm/i915: intel_frontbuffer_flush can now be static Paulo Zanoni
2015-07-08 21:08 ` [PATCH 2/3] drm/i915: fix intel_fb_obj_flush documentation Paulo Zanoni
2015-07-09 17:00   ` Rodrigo Vivi
2015-07-09 17:16     ` Daniel Vetter
2015-07-08 21:08 ` [PATCH 3/3] drm/i915: fix intel_frontbuffer_flip documentation Paulo Zanoni
2015-07-09 17:18   ` Daniel Vetter [this message]

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=20150709171818.GD7410@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=przanoni@gmail.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