qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Zhengui li <lizhengui@huawei.com>
Cc: kwolf@redhat.com, xieyingtai@huawei.com, qemu-block@nongnu.org,
	qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
	pbonzini@redhat.com
Subject: Re: [PATCH] vfio: fix incorrect print type
Date: Mon, 19 Oct 2020 07:47:45 -0600	[thread overview]
Message-ID: <20201019074745.4a72f8ac@w520.home> (raw)
In-Reply-To: <1603114337-28056-1-git-send-email-lizhengui@huawei.com>

On Mon, 19 Oct 2020 13:32:17 +0000
Zhengui li <lizhengui@huawei.com> wrote:

> fix incorrect print type.

Why is it incorrect, describe your change.  Patches must include a
Signed-off-by to adhere to the developer's certificate of origin.
Thanks,

Alex

> ---
>  hw/vfio/common.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 13471ae..acc3356 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -203,7 +203,7 @@ void vfio_region_write(void *opaque, hwaddr addr,
>          buf.qword = cpu_to_le64(data);
>          break;
>      default:
> -        hw_error("vfio: unsupported write size, %d bytes", size);
> +        hw_error("vfio: unsupported write size, %u bytes", size);
>          break;
>      }
>  
> @@ -260,7 +260,7 @@ uint64_t vfio_region_read(void *opaque,
>          data = le64_to_cpu(buf.qword);
>          break;
>      default:
> -        hw_error("vfio: unsupported read size, %d bytes", size);
> +        hw_error("vfio: unsupported read size, %u bytes", size);
>          break;
>      }
>  



  parent reply	other threads:[~2020-10-19 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 13:32 [PATCH] vfio: fix incorrect print type Zhengui li
2020-10-19 13:41 ` no-reply
2020-10-19 13:47 ` Alex Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-19 14:23 Zhengui li

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=20201019074745.4a72f8ac@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lizhengui@huawei.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xieyingtai@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 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).