All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: David Airlie <airlied@linux.ie>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v2 -next] drm/virtio: remove set but not used variable 'vgdev'
Date: Thu, 28 Mar 2019 11:32:09 +0100	[thread overview]
Message-ID: <20190328103209.wmdakmzmiwaxf7cx__19799.0813919873$1553769145$gmane$org@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190325092631.152060-1-yuehaibing@huawei.com>

On Mon, Mar 25, 2019 at 09:26:31AM +0000, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
> 
> drivers/gpu/drm/virtio/virtgpu_ttm.c: In function 'virtio_gpu_init_mem_type':
> drivers/gpu/drm/virtio/virtgpu_ttm.c:117:28: warning:
>  variable 'vgdev' set but not used [-Wunused-but-set-variable]
> 
> drivers/gpu/drm/virtio/virtgpu_ttm.c: In function 'virtio_gpu_bo_swap_notify':
> drivers/gpu/drm/virtio/virtgpu_ttm.c:300:28: warning:
>  variable 'vgdev' set but not used [-Wunused-but-set-variable]
> 
> It is never used since introduction in dc5698e80cf7 ("Add virtio gpu driver.")

Patch queued up.

thanks,
  Gerd

  parent reply	other threads:[~2019-03-28 10:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  2:15 [PATCH -next] drm/ttm: remove set but not used variable 'driver' YueHaibing
2018-11-08  2:15 ` YueHaibing
2018-11-08  2:15 ` YueHaibing
2018-11-08  2:17 ` Zhang, Jerry(Junwei)
2018-11-08  2:17   ` Zhang, Jerry(Junwei)
2018-11-08  2:17   ` Zhang, Jerry(Junwei)
2018-11-08  6:11 ` Huang, Ray
2018-11-08  6:11   ` Huang, Ray
2018-11-08  6:11   ` Huang, Ray
2018-11-08  8:17 ` Koenig, Christian
2018-11-08  8:17   ` Koenig, Christian
2018-11-08  8:17   ` Koenig, Christian
2019-03-20  1:51 ` [PATCH -next] drm/ttm: remove set but not used variable 'vgdev' YueHaibing
2019-03-20  2:03   ` YueHaibing
2019-03-20  2:03   ` YueHaibing
2019-03-25  9:02   ` Daniel Vetter
2019-03-25  9:02   ` Daniel Vetter
2019-03-25  9:02     ` Daniel Vetter
2019-03-25  9:11     ` YueHaibing
2019-03-25  9:11       ` YueHaibing
2019-03-25  9:11       ` YueHaibing
2019-03-25  9:26   ` [PATCH v2 -next] drm/virtio: " YueHaibing
2019-03-25  9:26     ` YueHaibing
2019-03-25 11:35     ` Mukesh Ojha
2019-03-25 11:35     ` Mukesh Ojha
2019-03-27 14:47     ` Mukesh Ojha
2019-03-27 14:47     ` Mukesh Ojha
2019-03-27 14:59       ` Mukesh Ojha
2019-03-28 10:32     ` Gerd Hoffmann [this message]
2019-03-28 10:32     ` Gerd Hoffmann
2019-03-28 10:32       ` Gerd Hoffmann
2019-02-18 13:59 [PATCH -next] drm/ttm: remove set but not used variable 'bdev' YueHaibing
2019-02-18 13:59 ` YueHaibing
2019-02-18 13:59 ` YueHaibing
2019-02-28  2:41 ` Alex Deucher
2019-02-28  2:41   ` Alex Deucher
2019-02-28  2:41   ` Alex Deucher
2019-03-20 12:59 [PATCH -next] drm/ttm: remove set but not used variable 'rdev' YueHaibing
2019-03-20 12:59 ` YueHaibing
2019-03-20 12:59 ` YueHaibing
2019-03-21 14:00 ` Alex Deucher
2019-03-21 14:00   ` Alex Deucher
2019-03-21 14:00   ` Alex Deucher

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='20190328103209.wmdakmzmiwaxf7cx__19799.0813919873$1553769145$gmane$org@sirius.home.kraxel.org' \
    --to=kraxel@redhat.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yuehaibing@huawei.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.