From: Eric Blake <eblake@redhat.com>
To: lijiejun <a_lijiejun@163.com>, kraxel@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] virtio-gpu: Add spaces around operator
Date: Tue, 9 Mar 2021 09:43:53 -0600 [thread overview]
Message-ID: <0a9ae121-8bd5-8457-c335-60e8fb0af02a@redhat.com> (raw)
In-Reply-To: <1615275756-129881-1-git-send-email-a_lijiejun@163.com>
On 3/9/21 1:42 AM, lijiejun wrote:
> Fix code style. Operator needs spaces forend sides, and delete line space.
What operator? 'break' is a statement, not an operator.
>
> Signed-off-by: lijiejun <a_lijiejun@163.com>
> ---
> hw/display/virtio-gpu-3d.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/hw/display/virtio-gpu-3d.c b/hw/display/virtio-gpu-3d.c
> index 9eb4890..d989648 100644
> --- a/hw/display/virtio-gpu-3d.c
> +++ b/hw/display/virtio-gpu-3d.c
> @@ -438,7 +438,7 @@ void virtio_gpu_virgl_process_cmd(VirtIOGPU *g,
> break;
> case VIRTIO_GPU_CMD_RESOURCE_FLUSH:
> virgl_cmd_resource_flush(g, cmd);
> - break;
> + break;
> case VIRTIO_GPU_CMD_RESOURCE_UNREF:
> virgl_cmd_resource_unref(g, cmd);
> break;
> @@ -456,7 +456,6 @@ void virtio_gpu_virgl_process_cmd(VirtIOGPU *g,
> case VIRTIO_GPU_CMD_GET_CAPSET:
> virgl_cmd_get_capset(g, cmd);
> break;
> -
> case VIRTIO_GPU_CMD_GET_DISPLAY_INFO:
> virtio_gpu_get_display_info(g, cmd);
> break;
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-03-09 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 7:42 [PATCH] virtio-gpu: Add spaces around operator lijiejun
2021-03-09 9:08 ` Philippe Mathieu-Daudé
2021-03-09 12:27 ` 李皆俊
2021-03-09 15:43 ` Eric Blake [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-09 3:57 李皆俊
2021-03-09 7:02 ` 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=0a9ae121-8bd5-8457-c335-60e8fb0af02a@redhat.com \
--to=eblake@redhat.com \
--cc=a_lijiejun@163.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).