From: Gurchetan Singh <gurchetansingh@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: Gurchetan Singh <gurchetansingh@chromium.org>, kraxel@redhat.com
Subject: [PATCH 1/9] drm/virtio: static-ify virtio_fence_signaled
Date: Tue, 17 Dec 2019 16:59:21 -0800 [thread overview]
Message-ID: <20191218005929.6709-2-gurchetansingh@chromium.org> (raw)
In-Reply-To: <20191218005929.6709-1-gurchetansingh@chromium.org>
Not used anywhere else.
Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 -
drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/virtgpu_drv.h
index eedae2a7b532..6b3f1551a2f1 100644
--- a/drivers/gpu/drm/virtio/virtgpu_drv.h
+++ b/drivers/gpu/drm/virtio/virtgpu_drv.h
@@ -350,7 +350,6 @@ struct drm_plane *virtio_gpu_plane_init(struct virtio_gpu_device *vgdev,
int index);
/* virtio_gpu_fence.c */
-bool virtio_fence_signaled(struct dma_fence *f);
struct virtio_gpu_fence *virtio_gpu_fence_alloc(
struct virtio_gpu_device *vgdev);
void virtio_gpu_fence_emit(struct virtio_gpu_device *vgdev,
diff --git a/drivers/gpu/drm/virtio/virtgpu_fence.c b/drivers/gpu/drm/virtio/virtgpu_fence.c
index a4b9881ca1d3..5466aab7d39a 100644
--- a/drivers/gpu/drm/virtio/virtgpu_fence.c
+++ b/drivers/gpu/drm/virtio/virtgpu_fence.c
@@ -37,7 +37,7 @@ static const char *virtio_get_timeline_name(struct dma_fence *f)
return "controlq";
}
-bool virtio_fence_signaled(struct dma_fence *f)
+static bool virtio_fence_signaled(struct dma_fence *f)
{
struct virtio_gpu_fence *fence = to_virtio_fence(f);
--
2.24.1.735.g03f4e72817-goog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-18 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 0:59 [PATCH 0/9] *** virtgpu cleanups *** Gurchetan Singh
2019-12-18 0:59 ` Gurchetan Singh [this message]
2019-12-18 0:59 ` [PATCH 2/9] drm/virtio: static-ify virtio_gpu_framebuffer_init Gurchetan Singh
2019-12-18 0:59 ` [PATCH 3/9] drm/virtio: get rid of drm_encoder_to_virtio_gpu_output Gurchetan Singh
2019-12-18 0:59 ` [PATCH 4/9] drm/virtio: simplify getting fake offset Gurchetan Singh
2019-12-18 0:59 ` [PATCH 5/9] drm/virtio: remove virtgpu_gem_prime_import_sg_table Gurchetan Singh
2019-12-18 0:59 ` [PATCH 6/9] drm/virtio: move to_virtio_fence inside virtgpu_fence Gurchetan Singh
2019-12-18 0:59 ` [PATCH 7/9] drm/virtio: move drm_connector_to_virtio_gpu_output to virtgpu_display Gurchetan Singh
2019-12-18 0:59 ` [PATCH 8/9] drm/virtio: split out vq functions from virtgpu_drv.h Gurchetan Singh
2019-12-18 0:59 ` [PATCH 9/9] drm/virtio: split out gem " Gurchetan Singh
2019-12-18 8:31 ` [PATCH 0/9] *** virtgpu cleanups *** Gerd Hoffmann
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=20191218005929.6709-2-gurchetansingh@chromium.org \
--to=gurchetansingh@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
/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.