[PATCH 1/3] drm/writeback: don't set fence->ops to default

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: LKML <linux-kernel@vger.kernel.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Subject: [PATCH 1/3] drm/writeback: don't set fence->ops to default
Date: Mon, 11 May 2020 11:11:40 +0200	[thread overview]
Message-ID: <20200511091142.208787-1-daniel.vetter@ffwll.ch> (raw)

It's the default.

Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
---
 drivers/gpu/drm/drm_writeback.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
index 43d9e3bb3a94..dccf4504f1bb 100644
--- a/drivers/gpu/drm/drm_writeback.c
+++ b/drivers/gpu/drm/drm_writeback.c
@@ -108,7 +108,6 @@ static const struct dma_fence_ops drm_writeback_fence_ops = {
 	.get_driver_name = drm_writeback_fence_get_driver_name,
 	.get_timeline_name = drm_writeback_fence_get_timeline_name,
 	.enable_signaling = drm_writeback_fence_enable_signaling,
-	.wait = dma_fence_default_wait,
 };
 
 static int create_writeback_properties(struct drm_device *dev)
-- 
2.26.2

WARNING: multiple messages have this Message-ID (diff)

From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: LKML <linux-kernel@vger.kernel.org>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH 1/3] drm/writeback: don't set fence->ops to default
Date: Mon, 11 May 2020 11:11:40 +0200	[thread overview]
Message-ID: <20200511091142.208787-1-daniel.vetter@ffwll.ch> (raw)

It's the default.

Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
---
 drivers/gpu/drm/drm_writeback.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
index 43d9e3bb3a94..dccf4504f1bb 100644
--- a/drivers/gpu/drm/drm_writeback.c
+++ b/drivers/gpu/drm/drm_writeback.c
@@ -108,7 +108,6 @@ static const struct dma_fence_ops drm_writeback_fence_ops = {
 	.get_driver_name = drm_writeback_fence_get_driver_name,
 	.get_timeline_name = drm_writeback_fence_get_timeline_name,
 	.enable_signaling = drm_writeback_fence_enable_signaling,
-	.wait = dma_fence_default_wait,
 };
 
 static int create_writeback_properties(struct drm_device *dev)
-- 
2.26.2

_______________________________________________
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: Daniel Vetter <daniel.vetter@ffwll.ch>
To: LKML <linux-kernel@vger.kernel.org>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Maxime Ripard <mripard@kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: [Intel-gfx] [PATCH 1/3] drm/writeback: don't set fence->ops to default
Date: Mon, 11 May 2020 11:11:40 +0200	[thread overview]
Message-ID: <20200511091142.208787-1-daniel.vetter@ffwll.ch> (raw)

It's the default.

Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
---
 drivers/gpu/drm/drm_writeback.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
index 43d9e3bb3a94..dccf4504f1bb 100644
--- a/drivers/gpu/drm/drm_writeback.c
+++ b/drivers/gpu/drm/drm_writeback.c
@@ -108,7 +108,6 @@ static const struct dma_fence_ops drm_writeback_fence_ops = {
 	.get_driver_name = drm_writeback_fence_get_driver_name,
 	.get_timeline_name = drm_writeback_fence_get_timeline_name,
 	.enable_signaling = drm_writeback_fence_enable_signaling,
-	.wait = dma_fence_default_wait,
 };
 
 static int create_writeback_properties(struct drm_device *dev)
-- 
2.26.2

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

next             reply	other threads:[~2020-05-11  9:11 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11  9:11 Daniel Vetter [this message]
2020-05-11  9:11 ` [Intel-gfx] [PATCH 1/3] drm/writeback: don't set fence->ops to default 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
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

find likely ancestor, descendant, or conflicting patches for this message:
dfblob:43d9e3bb3a9 dfblob:43d9e3bb3a9 dfblob:43d9e3bb3a9
dfblob:dccf4504f1b dfblob:dccf4504f1b dfblob:dccf4504f1b
	(help)

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=20200511091142.208787-1-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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.