From: Thomas Huth <1753437@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1753437] Re: qemu/pc-bios/s390-ccw/libc.c:82: bad test ?
Date: Mon, 12 Mar 2018 06:42:05 -0000 [thread overview]
Message-ID: <152083692535.7345.10962252346599581806.malone@soybean.canonical.com> (raw)
In-Reply-To: 152024589806.7327.9844777027357521578.malonedeb@gac.canonical.com
Looks like the mailing list <-> launchpad bridge again ignored mails to the corresponding mailing list thread. It's not a real bug, see here for details:
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg01142.html
I'll try to remember to clean this up the next time we update the s390-ccw bios.
** Changed in: qemu
Assignee: (unassigned) => Thomas Huth (th-huth)
** Changed in: qemu
Importance: Undecided => Low
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1753437
Title:
qemu/pc-bios/s390-ccw/libc.c:82: bad test ?
Status in QEMU:
Confirmed
Bug description:
qemu/pc-bios/s390-ccw/libc.c:82]: (style) Unsigned variable 'num_idx'
can't be negative so it is unnecessary to test it.
Source code is
while (num_idx >= 0) {
but
size_t num_idx = 1; /* account for NUL */
So there is no escape from the while loop.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1753437/+subscriptions
next prev parent reply other threads:[~2018-03-12 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 10:31 [Qemu-devel] [Bug 1753437] [NEW] qemu/pc-bios/s390-ccw/libc.c:82: bad test ? dcb
2018-03-05 11:22 ` Christian Borntraeger
2018-03-05 14:53 ` Thomas Huth
2018-03-05 15:30 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-03-12 6:42 ` Thomas Huth [this message]
2018-04-13 15:47 ` [Qemu-devel] [Bug 1753437] Re: pc-bios/s390-ccw/libc: size_t should be unsigned Thomas Huth
2018-05-04 14:00 ` Thomas Huth
2018-08-15 7:28 ` 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=152083692535.7345.10962252346599581806.malone@soybean.canonical.com \
--to=1753437@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.