From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linaro-mm-sig@lists.linaro.org,
Daniel Vetter <daniel.vetter@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] dma-fence: use default wait function for mock fences
Date: Mon, 11 May 2020 10:41:03 +0100 [thread overview]
Message-ID: <158919006380.1729.6928823811672806738@build.alporthouse.com> (raw)
In-Reply-To: <20200511091142.208787-2-daniel.vetter@ffwll.ch>
Quoting Daniel Vetter (2020-05-11 10:11:41)
> No need to micro-optmize when we're waiting in a mocked object ...
It's setting up the expected return values for the test.
-Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linaro-mm-sig@lists.linaro.org,
Daniel Vetter <daniel.vetter@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] dma-fence: use default wait function for mock fences
Date: Mon, 11 May 2020 10:41:03 +0100 [thread overview]
Message-ID: <158919006380.1729.6928823811672806738@build.alporthouse.com> (raw)
In-Reply-To: <20200511091142.208787-2-daniel.vetter@ffwll.ch>
Quoting Daniel Vetter (2020-05-11 10:11:41)
> No need to micro-optmize when we're waiting in a mocked object ...
It's setting up the expected return values for the test.
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linaro-mm-sig@lists.linaro.org,
Daniel Vetter <daniel.vetter@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 2/3] dma-fence: use default wait function for mock fences
Date: Mon, 11 May 2020 10:41:03 +0100 [thread overview]
Message-ID: <158919006380.1729.6928823811672806738@build.alporthouse.com> (raw)
In-Reply-To: <20200511091142.208787-2-daniel.vetter@ffwll.ch>
Quoting Daniel Vetter (2020-05-11 10:11:41)
> No need to micro-optmize when we're waiting in a mocked object ...
It's setting up the expected return values for the test.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-11 9:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 9:11 [PATCH 1/3] drm/writeback: don't set fence->ops to default Daniel Vetter
2020-05-11 9:11 ` [Intel-gfx] " Daniel Vetter
2020-05-11 9:11 ` Daniel Vetter
2020-05-11 9:11 ` [PATCH 2/3] dma-fence: use default wait function for mock fences Daniel Vetter
2020-05-11 9:11 ` [Intel-gfx] " Daniel Vetter
2020-05-11 9:11 ` Daniel Vetter
2020-05-11 9:41 ` Chris Wilson [this message]
2020-05-11 9:41 ` [Intel-gfx] " Chris Wilson
2020-05-11 9:41 ` Chris Wilson
2020-05-11 10:12 ` Daniel Vetter
2020-05-11 10:12 ` [Intel-gfx] " Daniel Vetter
2020-05-11 10:12 ` Daniel Vetter
2020-05-11 18:13 ` [Intel-gfx] " Ruhl, Michael J
2020-05-11 18:13 ` Ruhl, Michael J
2020-05-11 18:13 ` Ruhl, Michael J
2020-05-11 18:17 ` Ruhl, Michael J
2020-05-11 18:17 ` Ruhl, Michael J
2020-05-11 18:17 ` Ruhl, Michael J
2020-05-11 9:11 ` [PATCH 3/3] misc/habalabs: don't set default fence_ops->wait Daniel Vetter
2020-05-11 9:11 ` [Intel-gfx] " Daniel Vetter
2020-05-11 9:11 ` Daniel Vetter
2020-05-11 9:36 ` Oded Gabbay
2020-05-11 9:36 ` [Intel-gfx] " Oded Gabbay
2020-05-11 9:36 ` Oded Gabbay
2020-05-11 9:43 ` Oded Gabbay
2020-05-11 9:43 ` [Intel-gfx] " Oded Gabbay
2020-05-11 9:43 ` Oded Gabbay
2020-05-12 2:14 ` [Intel-gfx] " Dave Airlie
2020-05-12 2:14 ` Dave Airlie
2020-05-12 2:14 ` Dave Airlie
2020-05-12 6:12 ` Daniel Vetter
2020-05-12 6:12 ` Daniel Vetter
2020-05-12 6:12 ` Daniel Vetter
2020-05-14 11:38 ` Oded Gabbay
2020-05-14 11:38 ` Oded Gabbay
2020-05-14 11:38 ` Oded Gabbay
2020-05-20 18:04 ` Daniel Vetter
2020-05-20 18:04 ` Daniel Vetter
2020-05-20 18:04 ` Daniel Vetter
2020-05-20 18:09 ` Oded Gabbay
2020-05-20 18:09 ` Oded Gabbay
2020-05-20 18:09 ` Oded Gabbay
2020-05-11 9:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/writeback: don't set fence->ops to default Patchwork
2020-05-11 9:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-05-11 18:12 ` [PATCH 1/3] " Ruhl, Michael J
2020-05-11 18:12 ` [Intel-gfx] " Ruhl, Michael J
2020-05-11 18:12 ` Ruhl, Michael J
2020-05-20 18:03 ` Daniel Vetter
2020-05-20 18:03 ` [Intel-gfx] " Daniel Vetter
2020-05-20 18:03 ` Daniel Vetter
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=158919006380.1729.6928823811672806738@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.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 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.