Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: spelling fixes for frontbuffer tracking kerneldoc
Date: Wed, 1 Oct 2014 10:13:49 +0200	[thread overview]
Message-ID: <20141001081349.GK12343@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGQut+AgvyCXmLNLyefFFkS6dsDeXswNe1nPMm_JO5QWRA@mail.gmail.com>

On Tue, Sep 30, 2014 at 05:34:44PM -0300, Paulo Zanoni wrote:
> 2014-09-30 17:10 GMT-03:00 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > Oh well.
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> >  drivers/gpu/drm/i915/intel_drv.h         |  2 +-
> >  drivers/gpu/drm/i915/intel_frontbuffer.c | 13 ++++++-------
> >  2 files changed, 7 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> > index 91e2b128c537..4e71ae5e3832 100644
> > --- a/drivers/gpu/drm/i915/intel_drv.h
> > +++ b/drivers/gpu/drm/i915/intel_drv.h
> > @@ -816,7 +816,7 @@ void intel_frontbuffer_flip_complete(struct drm_device *dev,
> >  void intel_frontbuffer_flush(struct drm_device *dev,
> >                              unsigned frontbuffer_bits);
> >  /**
> > - * intel_frontbuffer_flip - prepare frontbuffer flip
> > + * intel_frontbuffer_flip - synchronous frontbuffer flip
> >   * @dev: DRM device
> >   * @frontbuffer_bits: frontbuffer plane tracking bits
> >   *
> > diff --git a/drivers/gpu/drm/i915/intel_frontbuffer.c b/drivers/gpu/drm/i915/intel_frontbuffer.c
> > index 969af6e7b634..437fa8072adf 100644
> > --- a/drivers/gpu/drm/i915/intel_frontbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_frontbuffer.c
> > @@ -28,7 +28,7 @@
> >   * DOC: frontbuffer tracking
> >   *
> >   * Many features require us to track changes to the currently active
> > - * frontbuffer, especially rendering targetted at the frontbuffer.
> > + * frontbuffer, especially rendering targeted at the frontbuffer.
> >   *
> >   * To be able to do so GEM tracks frontbuffers using a bitmask for all possible
> >   * frontbuffer slots through i915_gem_track_fb(). The function in this file are
> > @@ -55,7 +55,7 @@
> >   * cancelled as soon as busyness is detected.
> >   *
> >   * Note that there's also an older frontbuffer activity tracking scheme which
> > - * just trackings general activity. This is done by the various mark_busy and
> > + * just tracks general activity. This is done by the various mark_busy and
> >   * mark_idle functions. For display power management features using these
> >   * functions is deprecated and should be avoided.
> >   */
> > @@ -166,7 +166,7 @@ void intel_fb_obj_invalidate(struct drm_i915_gem_object *obj,
> >   *
> >   * This function gets called every time rendering on the given planes has
> >   * completed and frontbuffer caching can be started again. Flushes will get
> > - * delayed if they're blocked by some oustanding asynchronous rendering.
> > + * delayed if they're blocked by some outstanding asynchronous rendering.
> >   *
> >   * Can be called without any locks held.
> >   */
> > @@ -229,7 +229,7 @@ void intel_fb_obj_flush(struct drm_i915_gem_object *obj,
> >  }
> >
> >  /**
> > - * intel_frontbuffer_flip_prepare - prepare asnychronous frontbuffer flip
> > + * intel_frontbuffer_flip_prepare - prepare asynchronous frontbuffer flip
> >   * @dev: DRM device
> >   * @frontbuffer_bits: frontbuffer plane tracking bits
> >   *
> > @@ -253,12 +253,12 @@ void intel_frontbuffer_flip_prepare(struct drm_device *dev,
> >  }
> >
> >  /**
> > - * intel_frontbuffer_flip_complete - complete asynchronous frontbuffer flush
> > + * intel_frontbuffer_flip_complete - complete asynchronous frontbuffer flip
> >   * @dev: DRM device
> >   * @frontbuffer_bits: frontbuffer plane tracking bits
> >   *
> >   * This function gets called after the flip has been latched and will complete
> > - * on the next vblank. It will execute the fush if it hasn't been cancalled yet.
> > + * on the next vblank. It will execute the flush if it hasn't been cancalled yet.
> 
> The word "cancalled" could also be fixed :)

Fixed.
> 
> With that: Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>

Thanks for your review, both patches applied.
-Daniel

> 
> >   *
> >   * Can be called without any locks held.
> >   */
> > @@ -275,4 +275,3 @@ void intel_frontbuffer_flip_complete(struct drm_device *dev,
> >
> >         intel_frontbuffer_flush(dev, frontbuffer_bits);
> >  }
> > -
> > --
> > 2.1.1
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> 
> 
> -- 
> Paulo Zanoni

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-10-01  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 20:10 [PATCH 1/2] drm/i915: Tighting frontbuffer tracking around flips Daniel Vetter
2014-09-30 20:10 ` [PATCH 2/2] drm/i915: spelling fixes for frontbuffer tracking kerneldoc Daniel Vetter
2014-09-30 20:34   ` Paulo Zanoni
2014-10-01  8:13     ` Daniel Vetter [this message]
2014-09-30 20:26 ` [PATCH 1/2] drm/i915: Tighting frontbuffer tracking around flips Paulo Zanoni

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=20141001081349.GK12343@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --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