[Mesa-dev] [PATCH 3/5] anv: Fix some comment typos.

Jason Ekstrand jason at jlekstrand.net
Wed Sep 20 03:11:17 UTC 2017


rb

On Tue, Sep 19, 2017 at 11:06 AM, Eric Anholt <eric at anholt.net> wrote:

> ---
>  src/intel/vulkan/anv_private.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/intel/vulkan/anv_private.h b/src/intel/vulkan/anv_
> private.h
> index df8de8d9407c..2808a5e991e7 100644
> --- a/src/intel/vulkan/anv_private.h
> +++ b/src/intel/vulkan/anv_private.h
> @@ -1895,7 +1895,7 @@ struct anv_fence_impl {
>  struct anv_fence {
>     /* Permanent fence state.  Every fence has some form of permanent state
>      * (type != ANV_SEMAPHORE_TYPE_NONE).  This may be a BO to fence on
> (for
> -    * cross-process fences0 or it could just be a dummy for use
> internally.
> +    * cross-process fences) or it could just be a dummy for use
> internally.
>      */
>     struct anv_fence_impl permanent;
>
> @@ -1933,13 +1933,13 @@ struct anv_semaphore_impl {
>         */
>        struct anv_bo *bo;
>
> -      /* The sync file descriptor when type ==
> AKV_SEMAPHORE_TYPE_SYNC_FILE.
> +      /* The sync file descriptor when type ==
> ANV_SEMAPHORE_TYPE_SYNC_FILE.
>         * If the semaphore is in the unsignaled state due to either just
> being
>         * created or because it has been used for a wait, fd will be -1.
>         */
>        int fd;
>
> -      /* Sync object handle when type == AKV_SEMAPHORE_TYPE_DRM_SYNCOBJ.
> +      /* Sync object handle when type == ANV_SEMAPHORE_TYPE_DRM_SYNCOBJ.
>         * Unlike GEM BOs, DRM sync objects aren't deduplicated by the
> kernel on
>         * import so we don't need to bother with a userspace cache.
>         */
> --
> 2.14.1
>
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170919/e2ecae77/attachment.html>


More information about the mesa-dev mailing list