From: Peter Maydell <peter.maydell@linaro.org>
To: Amit Shah <amit.shah@redhat.com>
Cc: John Snow <jsnow@redhat.com>, qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL for-2.1] virtio-rng: Fix abort on invalid input
Date: Thu, 17 Jul 2014 13:49:19 +0100 [thread overview]
Message-ID: <CAFEAcA8FxKmrXR_X2-3-PQf9DuZoJSsWKCQ+cxzEYYC4NOYFRg@mail.gmail.com> (raw)
In-Reply-To: <20140716091327.GD22288@grmbl.mre>
On 16 July 2014 10:13, Amit Shah <amit.shah@redhat.com> wrote:
> Hi,
>
> This patch returns an error instead of aborting, which is desirable
> not just for cmdline invocation, but prevents an abort in case of
> device hotplug.
>
> Patch is small, and reviewed on-list.
>
> Please pull,
>
> The following changes since commit 5a7348045091a2bc15d85bb177e5956aa6114e5a:
>
> Update version for v2.1.0-rc2 release (2014-07-15 18:55:37 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-rng.git for-2.1
>
> for you to fetch changes up to 9ef6be93250e46d35062c84d5c75c7cb515dc27c:
>
> virtio-rng: Add human-readable error message for negative max-bytes parameter (2014-07-16 14:25:29 +0530)
Hi. I'm afraid this doesn't build on 32-bit hosts:
CC hw/virtio/virtio-rng.o
/root/qemu/hw/virtio/virtio-rng.c: In function 'virtio_rng_device_realize':
/root/qemu/hw/virtio/virtio-rng.c:186:19: error: format '%lld' expects
argument of type 'long long int', but argument 7 has type 'long int'
[-Werror=format]
cc1: all warnings being treated as errors
I think you want "(int64_t)0" rather than "0L".
thanks
-- PMM
prev parent reply other threads:[~2014-07-17 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 9:13 [Qemu-devel] [PULL for-2.1] virtio-rng: Fix abort on invalid input Amit Shah
2014-07-17 12:49 ` 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=CAFEAcA8FxKmrXR_X2-3-PQf9DuZoJSsWKCQ+cxzEYYC4NOYFRg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=amit.shah@redhat.com \
--cc=jsnow@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).