From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Bug 1801073 <1801073@bugs.launchpad.net>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1801073] Re: util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but has parameter of type 'int' which may cause truncation of value [-Werror=absolute-value]
Date: Mon, 21 Jan 2019 15:35:45 +0100 [thread overview]
Message-ID: <20190121143545.su4ondup4a7go2h5@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA9uJ7+T64u1HSztCweJhqEDpctmohFnmCyKRD8B_sLnzg@mail.gmail.com>
On Mon, Jan 21, 2019 at 12:57:16PM +0000, Peter Maydell wrote:
> On Mon, 21 Jan 2019 at 12:47, Martin Liska <mliska@suse.cz> wrote:
> >
> > Should be fixed here:
> > http://git.ipxe.org/ipxe.git/commitdiff/956f6a722
> >
> > Btw. how do you pull changes from ipxe into qemu repo?
>
> The next step is a QEMU patch which updates our git submodule
> to point at a version of IPXE with the fix and also has the
> pre-built binaries corresponding to that new version.
>
> Gerd, it looks like you did the last IPXE update -- could
> we do another one with this fix in it?
Yes, makes sense to do that, last ipxe rebase was more than a year ago.
cheers,
Gerd
next prev parent reply other threads:[~2019-01-21 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:18 [Qemu-devel] [Bug 1801073] [NEW] util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but has parameter of type 'int' which may cause truncation of value [-Werror=absolute-value] Martin Liska
2018-12-05 11:40 ` [Qemu-devel] [Bug 1801073] " Alex Bennée
2019-01-18 17:22 ` Peter Maydell
2019-01-21 9:41 ` Martin Liska
2019-01-21 12:25 ` Martin Liska
2019-01-21 12:57 ` Peter Maydell
2019-01-21 14:35 ` Gerd Hoffmann [this message]
2019-04-24 6:06 ` Thomas Huth
2019-04-24 6:06 ` Thomas Huth
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=20190121143545.su4ondup4a7go2h5@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=1801073@bugs.launchpad.net \
--cc=peter.maydell@linaro.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).