From: Sumit Semwal <sumit.semwal@linaro.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] dma-buf/fence: make timeout handling in fence_default_wait consistent (v2)
Date: Wed, 9 Nov 2016 01:05:35 +0530 [thread overview]
Message-ID: <CAO_48GEYmw5VcuFg0natrorSBRVTyuYfH014iFUD30-EWyqhYg@mail.gmail.com> (raw)
In-Reply-To: <1478553376-18575-1-git-send-email-alexander.deucher@amd.com>
Hi Alex, Christian,
On 8 November 2016 at 02:46, Alex Deucher <alexdeucher@gmail.com> wrote:
> Kernel functions taking a timeout usually return 1 on success even
> when they get a zero timeout.
>
> v2: agd: rebase on drm-next
>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> Signen-off-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>
> These are the same patches Christian sent out previously, just
> rebased on the fence naming changes in drm-next.
>
Series applied to drm-misc; Thanks!
Best,
Sumit.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-11-08 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 21:16 [PATCH 1/4] dma-buf/fence: make timeout handling in fence_default_wait consistent (v2) Alex Deucher
[not found] ` <1478553376-18575-1-git-send-email-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2016-11-07 21:16 ` [PATCH 2/4] dma-buf/fence: revert "don't wait when specified timeout is zero" (v2) Alex Deucher
2016-11-07 21:16 ` [PATCH 3/4] drm/ttm: fix ttm_bo_wait Alex Deucher
2016-11-07 21:16 ` [PATCH 4/4] reservation: revert "wait only with non-zero timeout specified (v3)" v2 Alex Deucher
2016-11-08 0:50 ` Gustavo Padovan
2016-11-08 19:35 ` Sumit Semwal [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=CAO_48GEYmw5VcuFg0natrorSBRVTyuYfH014iFUD30-EWyqhYg@mail.gmail.com \
--to=sumit.semwal@linaro.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).