From: Gurchetan Singh <gurchetansingh@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: kraxel@redhat.com, Gurchetan Singh <gurchetansingh@chromium.org>
Subject: [PATCH 3/6] drm/virtio: get rid of drm_encoder_to_virtio_gpu_output
Date: Wed, 18 Dec 2019 16:57:30 -0800 [thread overview]
Message-ID: <20191219005733.18960-3-gurchetansingh@chromium.org> (raw)
In-Reply-To: <20191219005733.18960-1-gurchetansingh@chromium.org>
Not used anywhere.
Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/virtgpu_drv.h
index cf09e4af2fc5..3e0580a8d818 100644
--- a/drivers/gpu/drm/virtio/virtgpu_drv.h
+++ b/drivers/gpu/drm/virtio/virtgpu_drv.h
@@ -137,8 +137,6 @@ struct virtio_gpu_output {
container_of(x, struct virtio_gpu_output, crtc)
#define drm_connector_to_virtio_gpu_output(x) \
container_of(x, struct virtio_gpu_output, conn)
-#define drm_encoder_to_virtio_gpu_output(x) \
- container_of(x, struct virtio_gpu_output, enc)
struct virtio_gpu_framebuffer {
struct drm_framebuffer base;
--
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-19 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 0:57 [PATCH 1/6] drm/virtio: static-ify virtio_fence_signaled Gurchetan Singh
2019-12-19 0:57 ` [PATCH 2/6] drm/virtio: static-ify virtio_gpu_framebuffer_init Gurchetan Singh
2019-12-19 0:57 ` Gurchetan Singh [this message]
2019-12-19 0:57 ` [PATCH 4/6] drm/virtio: simplify getting fake offset Gurchetan Singh
2019-12-19 0:57 ` [PATCH 5/6] drm/virtio: move to_virtio_fence inside virtgpu_fence Gurchetan Singh
2019-12-19 0:57 ` [PATCH 6/6] drm/virtio: move drm_connector_to_virtio_gpu_output to virtgpu_display Gurchetan Singh
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=20191219005733.18960-3-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.