From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/2] Add TAILQ_FOREACH_SAFE
Date: Mon, 24 Nov 2008 12:35:08 +0100 [thread overview]
Message-ID: <492A916C.9080704@siemens.com> (raw)
In-Reply-To: <20081120132741.GB11616@shareable.org>
Jamie Lokier wrote:
> Anthony Liguori wrote:
>> Wouldn't:
>>
>> (var) ? ({ (next_var) = ((var)->field.tqe_next); 1;}) :0;
>>
>> Be equivalent to:
>>
>> (var) ? ((next_var = ((var)->field.tqe_next), var) : var
>
> Simpler:
>
> (var) && ((next_var) = (var)->field.tqe_next, 1)
>
Yes, indeed!
Anthony, could you merge this one and its application patch? I need both
of them for my kvm series.
Jan
-------------->
Add TAILQ iterator that allows to safely remove elements while walking
the list.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
sys-queue.h | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/sys-queue.h b/sys-queue.h
index 3d0773e..ad5c8fb 100644
--- a/sys-queue.h
+++ b/sys-queue.h
@@ -210,6 +210,11 @@ struct { \
(var); \
(var) = ((var)->field.tqe_next))
+#define TAILQ_FOREACH_SAFE(var, head, field, next_var) \
+ for ((var) = ((head)->tqh_first); \
+ (var) && ((next_var) = ((var)->field.tqe_next), 1); \
+ (var) = (next_var))
+
#define TAILQ_FOREACH_REVERSE(var, head, headname, field) \
for ((var) = (*(((struct headname *)((head)->tqh_last))->tqh_last)); \
(var); \
next prev parent reply other threads:[~2008-11-24 16:07 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 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
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
2008-11-20 13:21 ` Jan Kiszka
2008-11-20 13:27 ` Jamie Lokier
2008-11-24 11:35 ` Jan Kiszka [this message]
2008-11-25 22:05 ` 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=492A916C.9080704@siemens.com \
--to=jan.kiszka@siemens.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).