From: Markus Armbruster <armbru@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qdev: switch device and bus lists from LIST to TAILQ
Date: Tue, 25 Aug 2009 14:26:37 +0200 [thread overview]
Message-ID: <87d46k3wqq.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <1251193798-14984-1-git-send-email-kraxel@redhat.com> (Gerd Hoffmann's message of "Tue\, 25 Aug 2009 11\:49\:58 +0200")
Gerd Hoffmann <kraxel@redhat.com> writes:
> Tail queues allow to append elements to the tail if the list.
> That way we can maintain the ordering, i.e. devices/busses
> created first are also first in the list.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Looks good to me. I've always found the lists in reverted order
somewhat annoying.
prev parent reply other threads:[~2009-08-25 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 9:49 [Qemu-devel] [PATCH] qdev: switch device and bus lists from LIST to TAILQ Gerd Hoffmann
2009-08-25 12:26 ` Markus Armbruster [this message]
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=87d46k3wqq.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=kraxel@redhat.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).