All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Tsirkin <mst@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] drm/virtio: virtgpu_dmabuf_ops can be static
Date: Thu, 04 Jun 2020 14:40:43 -0400	[thread overview]
Message-ID: <20200604144025-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200531100457.GA195395@936ae0323f7b>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

On Sun, May 31, 2020 at 06:04:57PM +0800, kbuild test robot wrote:
> 
> Signed-off-by: kbuild test robot <lkp@intel.com>


Acked-by: Michael S. Tsirkin <mst@redhat.com>

Who's merging this?

> ---
>  virtgpu_prime.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/virtio/virtgpu_prime.c b/drivers/gpu/drm/virtio/virtgpu_prime.c
> index a753bb70fcf11..04848a768e74d 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_prime.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_prime.c
> @@ -43,7 +43,7 @@ static int virtgpu_virtio_get_uuid(struct dma_buf *buf,
>  	return 0;
>  }
>  
> -const struct virtio_dma_buf_ops virtgpu_dmabuf_ops =  {
> +static const struct virtio_dma_buf_ops virtgpu_dmabuf_ops =  {
>  	.ops = {
>  		.cache_sgt_mapping = true,
>  		.attach = virtio_dma_buf_attach,

  reply	other threads:[~2020-06-04 18:40 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 10:58 [virtio-dev] [PATCH v4 0/3] Support virtio cross-device resources David Stevens
2020-05-26 10:58 ` David Stevens
2020-05-26 10:58 ` David Stevens
2020-05-26 10:58 ` [virtio-dev] [PATCH v4 1/3] virtio: add dma-buf support for exported objects David Stevens
2020-05-26 10:58   ` David Stevens
2020-05-26 10:58   ` David Stevens
2020-06-04 19:05   ` [virtio-dev] " Michael S. Tsirkin
2020-06-04 19:05     ` Michael S. Tsirkin
2020-06-04 19:05     ` Michael S. Tsirkin
2020-06-05  1:28     ` [virtio-dev] " David Stevens
2020-06-05  1:28       ` David Stevens
2020-06-05  1:28       ` David Stevens
2020-06-06 20:04       ` [virtio-dev] " Michael S. Tsirkin
2020-06-06 20:04         ` Michael S. Tsirkin
2020-06-06 20:04         ` Michael S. Tsirkin
2020-06-08  1:33         ` [virtio-dev] " David Stevens
2020-06-08  1:33           ` David Stevens
2020-06-08  1:33           ` David Stevens
2020-06-08  6:00           ` [virtio-dev] " Michael S. Tsirkin
2020-06-08  6:00             ` Michael S. Tsirkin
2020-06-08  6:00             ` Michael S. Tsirkin
2020-06-08  8:32             ` [virtio-dev] " David Stevens
2020-06-08  8:32               ` David Stevens
2020-06-08  8:32               ` David Stevens
2020-06-08  9:05               ` [virtio-dev] " Michael S. Tsirkin
2020-06-08  9:05                 ` Michael S. Tsirkin
2020-06-08  9:05                 ` Michael S. Tsirkin
2020-06-08  9:30                 ` [virtio-dev] " David Stevens
2020-06-08  9:30                   ` David Stevens
2020-06-08  9:30                   ` David Stevens
2020-06-18 12:28     ` [virtio-dev] " Guennadi Liakhovetski
2020-06-18 12:28       ` Guennadi Liakhovetski
2020-06-18 12:28       ` Guennadi Liakhovetski
2020-06-18 12:28       ` Guennadi Liakhovetski
2020-06-19  1:57       ` [virtio-dev] " David Stevens
2020-06-19  1:57         ` David Stevens
2020-06-19  1:57         ` David Stevens
2020-06-19  6:53         ` [virtio-dev] " Guennadi Liakhovetski
2020-06-19  6:53           ` Guennadi Liakhovetski
2020-06-19  6:53           ` Guennadi Liakhovetski
2020-05-26 10:58 ` [virtio-dev] [PATCH v4 2/3] virtio-gpu: add VIRTIO_GPU_F_RESOURCE_UUID feature David Stevens
2020-05-26 10:58   ` David Stevens
2020-05-26 10:58   ` David Stevens
2020-05-26 10:58 ` [virtio-dev] [PATCH v4 3/3] drm/virtio: Support virtgpu exported resources David Stevens
2020-05-26 10:58   ` David Stevens
2020-05-26 10:58   ` David Stevens
2020-05-31 10:04   ` kbuild test robot
2020-05-31 10:04   ` [RFC PATCH] drm/virtio: virtgpu_dmabuf_ops can be static kbuild test robot
2020-06-04 18:40     ` Michael S. Tsirkin [this message]
2020-05-28  8:31 ` [virtio-dev] Re: [PATCH v4 0/3] Support virtio cross-device resources Gerd Hoffmann
2020-05-28  8:31   ` Gerd Hoffmann
2020-05-28  8:31   ` 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=20200604144025-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=kbuild-all@lists.01.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.