qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/5] 9p patches 2020-01-14
Date: Fri, 17 Jan 2020 12:12:03 +0000	[thread overview]
Message-ID: <CAFEAcA_64te7d16=8FnT9455vCwzqDxw+299voteTb7t3yZx8Q@mail.gmail.com> (raw)
In-Reply-To: <20200114160235.308040-1-groug@kaod.org>

On Tue, 14 Jan 2020 at 16:02, Greg Kurz <groug@kaod.org> wrote:
>
> The following changes since commit 3c8a6575985b1652b45bfa670b5e1907d642cfa0:
>
>   Merge remote-tracking branch 'remotes/kraxel/tags/usb-20200113-pull-request' into staging (2020-01-13 14:19:57 +0000)
>
> are available in the Git repository at:
>
>   https://github.com/gkurz/qemu.git tags/9p-next-2020-01-14
>
> for you to fetch changes up to fa0f22026747fe0ea6ef4b86c4e73e2e0965f05b:
>
>   9pfs/9p.c: remove unneeded labels (2020-01-14 07:59:47 +0100)
>
> ----------------------------------------------------------------
> Assorted fixes and cleanups.
>
> ----------------------------------------------------------------

Compile failure on 32-bit:

/home/peter.maydell/qemu/hw/9pfs/9p.c: In function 'v9fs_xattr_read':
/home/peter.maydell/qemu/hw/9pfs/9p.c:2140:54: error: passing argument
4 of 'v9fs_init_qiov_from_pdu' from incompatible pointer type
[-Werror=incompatible-pointer-types]
     v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset, &read_count, false);
                                                      ^
/home/peter.maydell/qemu/hw/9pfs/9p.c:2092:13: note: expected 'size_t
* {aka unsigned int *}' but argument is of type 'uint64_t * {aka long
long unsigned int *}'
 static void v9fs_init_qiov_from_pdu(QEMUIOVector *qiov, V9fsPDU *pdu,
             ^~~~~~~~~~~~~~~~~~~~~~~

thanks
-- PMM


      parent reply	other threads:[~2020-01-17 12:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 16:02 [PULL 0/5] 9p patches 2020-01-14 Greg Kurz
2020-01-14 16:02 ` [PULL 1/5] 9pfs: local: Fix possible memory leak in local_link() Greg Kurz
2020-01-14 16:02 ` [PULL 2/5] 9p: local: always return -1 on error in local_unlinkat_common Greg Kurz
2020-01-14 16:02 ` [PULL 3/5] 9p: init_in_iov_from_pdu can truncate the size Greg Kurz
2020-01-14 16:02 ` [PULL 4/5] virtfs-proxy-helper.c: remove 'err_out' label in setugid() Greg Kurz
2020-01-14 16:02 ` [PULL 5/5] 9pfs/9p.c: remove unneeded labels Greg Kurz
2020-01-17 12:12 ` Peter Maydell [this message]

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='CAFEAcA_64te7d16=8FnT9455vCwzqDxw+299voteTb7t3yZx8Q@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=groug@kaod.org \
    --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).