From: Thomas Huth <1904464@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1904464] Re: Build fails with 64 bits time_t
Date: Tue, 17 Nov 2020 10:51:25 -0000 [thread overview]
Message-ID: <160561028601.30031.1273354227634249725.malone@gac.canonical.com> (raw)
In-Reply-To: 160555959985.17306.1370815502265671907.malonedeb@wampee.canonical.com
Please send patches to the qemu-devel mailing list (and CC: the
corresponding maintainers) for proper review of your patch. See
https://wiki.qemu.org/Contribute/SubmitAPatch for details. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1904464
Title:
Build fails with 64 bits time_t
Status in QEMU:
New
Bug description:
time element is deprecated on new input_event structure in kernel's
input.h [1]
This will avoid the following build failure:
hw/input/virtio-input-host.c: In function 'virtio_input_host_handle_status':
hw/input/virtio-input-host.c:198:28: error: 'struct input_event' has no member named 'time'
198 | if (gettimeofday(&evdev.time, NULL)) {
| ^
Fixes:
- http://autobuild.buildroot.org/results/a538167e288c14208d557cd45446df86d3d599d5
- http://autobuild.buildroot.org/results/efd4474fb4b6c0ce0ab3838ce130429c51e43bbb
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=152194fe9c3f
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1904464/+subscriptions
next prev parent reply other threads:[~2020-11-17 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:46 [Bug 1904464] [NEW] Build fails with 64 bits time_t Fabrice Fontaine
2020-11-17 10:51 ` Thomas Huth [this message]
2021-05-10 4:28 ` [Bug 1904464] " Thomas Huth
2021-05-10 6:07 ` 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=160561028601.30031.1273354227634249725.malone@gac.canonical.com \
--to=1904464@bugs.launchpad.net \
--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).