From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/2] Add TAILQ_FOREACH_SAFE
Date: Wed, 19 Nov 2008 10:48:54 -0600 [thread overview]
Message-ID: <49244376.7020009@codemonkey.ws> (raw)
In-Reply-To: <492435B9.3010106@siemens.com>
Jan Kiszka wrote:
> Won't fly, next_var can become NULL and would be dereferenced without a
> prior check. Unless I'm totally blind now, there is no
> TAILQ_FOREACH_SAFE without "GCC-ism"
Wouldn't:
(var) ? ({ (next_var) = ((var)->field.tqe_next); 1;}) :0;
Be equivalent to:
(var) ? ((next_var = ((var)->field.tqe_next), var) : var
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-11-19 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 13:48 [Qemu-devel] [PATCH 0/2] Use TAILQ for breakpoints Jan Kiszka
2008-11-19 13:48 ` [Qemu-devel] [PATCH 1/2] Add TAILQ_FOREACH_SAFE Jan Kiszka
2008-11-19 15:00 ` Anthony Liguori
2008-11-19 15:50 ` [Qemu-devel] " Jan Kiszka
2008-11-19 16:48 ` Anthony Liguori [this message]
2008-11-20 13:21 ` Jan Kiszka
2008-11-20 13:27 ` Jamie Lokier
2008-11-24 11:35 ` Jan Kiszka
2008-11-25 22:05 ` Anthony Liguori
2008-11-19 13:48 ` [Qemu-devel] [PATCH 2/2] Use sys-queue.h for break/watchpoint managment Jan Kiszka
2008-11-19 15:01 ` Anthony Liguori
2008-11-25 22:14 ` Anthony Liguori
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=49244376.7020009@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.