diff for duplicates of <53CF6128.6010703@amd.com> diff --git a/a/1.txt b/N1/1.txt index bc2f0a3..2a50af4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,6 +1,6 @@ Am 23.07.2014 09:09, schrieb Daniel Vetter: > On Wed, Jul 23, 2014 at 9:06 AM, Maarten Lankhorst -> <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> wrote: +> <maarten.lankhorst@canonical.com> wrote: >>> Can we somehow avoid the need to call fence_signal() at all? The interrupts at least on radeon are way to unreliable for such a thing. Can enable_signalling fail? What's the reason for fence_signaled() in the first place? >> It doesn't need to be completely reliable, or finish immediately. >> diff --git a/a/content_digest b/N1/content_digest index 32f3f63..58b3183 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,25 +15,25 @@ "ref\053CF5B9F.1050800@amd.com\0" "ref\053CF5EFE.6070307@canonical.com\0" "ref\0CAKMK7uHijSve_CsDE+pUk8+tjCAZjL7-nZCKeUkKuuufCPS4tQ@mail.gmail.com\0" - "ref\0CAKMK7uHijSve_CsDE+pUk8+tjCAZjL7-nZCKeUkKuuufCPS4tQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" - "From\0Christian K\303\266nig <christian.koenig-5C7GfCeVMHo@public.gmane.org>\0" - "Subject\0Re: [PATCH 09/17] drm/radeon: use common fence implementation for fences\0" + "From\0Christian K\303\266nig <christian.koenig@amd.com>\0" + "Subject\0Re: [Nouveau] [PATCH 09/17] drm/radeon: use common fence implementation for fences\0" "Date\0Wed, 23 Jul 2014 09:15:52 +0200\0" - "To\0Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>" - " Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>\0" - "Cc\0Thomas Hellstrom <thellstrom-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>" - nouveau <nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org> - LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> - dri-devel <dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org> - " Christian K\303\266nig <deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>" - Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + "To\0Daniel Vetter <daniel.vetter@ffwll.ch>" + " Maarten Lankhorst <maarten.lankhorst@canonical.com>\0" + "Cc\0Christian K\303\266nig <deathsimple@vodafone.de>" + Dave Airlie <airlied@gmail.com> + Thomas Hellstrom <thellstrom@vmware.com> + nouveau <nouveau@lists.freedesktop.org> + LKML <linux-kernel@vger.kernel.org> + dri-devel <dri-devel@lists.freedesktop.org> + Ben Skeggs <bskeggs@redhat.com> Deucher - " Alexander <alexander.deucher-5C7GfCeVMHo@public.gmane.org>\0" + " Alexander <alexander.deucher@amd.com>\0" "\00:1\0" "b\0" "Am 23.07.2014 09:09, schrieb Daniel Vetter:\n" "> On Wed, Jul 23, 2014 at 9:06 AM, Maarten Lankhorst\n" - "> <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> wrote:\n" + "> <maarten.lankhorst@canonical.com> wrote:\n" ">>> Can we somehow avoid the need to call fence_signal() at all? The interrupts at least on radeon are way to unreliable for such a thing. Can enable_signalling fail? What's the reason for fence_signaled() in the first place?\n" ">> It doesn't need to be completely reliable, or finish immediately.\n" ">>\n" @@ -63,4 +63,4 @@ "\n" > -Daniel -6dc85e841a7810357eb1b59a54b33f0ae816ce441a2beb14b26680cfeb984d98 +3ac84f4ca514e2ae7a385f3ae1eb6c74a627b6ce72e01885185a38370a4ba8f3
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.