qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: peter crosthwaite <peter.crosthwaite@xilinx.com>
Cc: edgar iglesias <edgar.iglesias@gmail.com>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org,
	qemu-trival@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 1/1] glib: Fix some misuses of gsize/size_t types
Date: Wed, 22 May 2013 02:03:05 -0400 (EDT)	[thread overview]
Message-ID: <1514690342.5631967.1369202585862.JavaMail.root@redhat.com> (raw)
In-Reply-To: <926326e96fd8685d74e9d5bf430fe4ad97a55289.1369191585.git.peter.crosthwaite@xilinx.com>



----- Messaggio originale -----
> Da: "peter crosthwaite" <peter.crosthwaite@xilinx.com>
> A: qemu-devel@nongnu.org
> Cc: pbonzini@redhat.com, aliguori@us.ibm.com, "edgar iglesias" <edgar.iglesias@gmail.com>
> Inviato: Mercoledì, 22 maggio 2013 5:01:43
> Oggetto: [PATCH v1 1/1] glib: Fix some misuses of gsize/size_t types
> 
> From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> 
> This unbreaks cross compile builds:
> 
> configure --target-list="i386-softmmu" --cpu=i386
> 
> When building on a 64bit machine.
> 
> Reported-by: David Holsgrove <david.holsgrove@xilinx.com>
> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> ---
> 
>  hw/nvram/fw_cfg.c | 4 ++--
>  qemu-char.c       | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/fw_cfg.c
> index 1a7e49c..479113b 100644
> --- a/hw/nvram/fw_cfg.c
> +++ b/hw/nvram/fw_cfg.c
> @@ -54,7 +54,7 @@ struct FWCfgState {
>  #define JPG_FILE 0
>  #define BMP_FILE 1
>  
> -static char *read_splashfile(char *filename, size_t *file_sizep,
> +static char *read_splashfile(char *filename, gsize *file_sizep,
>                               int *file_typep)
>  {
>      GError *err = NULL;
> @@ -112,7 +112,7 @@ static void fw_cfg_bootsplash(FWCfgState *s)
>      const char *boot_splash_filename = NULL;
>      char *p;
>      char *filename, *file_data;
> -    size_t file_size;
> +    gsize file_size;
>      int file_type;
>      const char *temp;
>  
> diff --git a/qemu-char.c b/qemu-char.c
> index cff2896..5d20d3c 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -2920,7 +2920,7 @@ void qmp_ringbuf_write(const char *device, const char
> *data,
>      CharDriverState *chr;
>      const uint8_t *write_data;
>      int ret;
> -    size_t write_count;
> +    gsize write_count;
>  
>      chr = qemu_chr_find(device);
>      if (!chr) {
> --
> 1.8.3.rc1.44.gb387c77.dirty
> 
> 

Adding qemu-trivial...

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

  reply	other threads:[~2013-05-22  6:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  3:01 [Qemu-devel] [PATCH v1 1/1] glib: Fix some misuses of gsize/size_t types peter.crosthwaite
2013-05-22  6:03 ` Paolo Bonzini [this message]
2013-05-22  6:25   ` Edgar E. Iglesias
2013-05-22 22:57 ` Anthony Liguori

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=1514690342.5631967.1369202585862.JavaMail.root@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trival@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).