From: Alexey Korolev <alexey.korolev@endace.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: sfd@endace.com, kevin@koconnor.net, seabios@seabios.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH 1/4] Add basic linked list operations
Date: Thu, 29 Mar 2012 15:03:43 +1300 [thread overview]
Message-ID: <4F73C2FF.5000709@endace.com> (raw)
In-Reply-To: <4F73228B.4050804@redhat.com>
>> This linked list implementation is partially based on kernel code. So it
>> should be quite stable
> How about just copying the file?
>
> I've used the linux kernel list implementation elsewhere too and it
> worked just fine with only minor tweaks (remove some likely()/unlikely()
> macros IIRC).
Right, in "take-2" Kevin has suggested very similar.
It will be done as a separate patch, because the changes are not just about pciinit.c, they also simplify
pmm.c and stack.c a bit. In this patch I'm submitting only few necessary functions for list operations.
next prev parent reply other threads:[~2012-03-29 2:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 4:25 [Qemu-devel] [PATCH 0/4] Redesign of pciinit.c (take 3) Alexey Korolev
2012-03-28 4:28 ` [Qemu-devel] [PATCH 1/4] Add basic linked list operations Alexey Korolev
2012-03-28 14:39 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2012-03-29 2:03 ` Alexey Korolev [this message]
2012-03-29 2:27 ` Kevin O'Connor
2012-03-29 10:41 ` Ian Campbell
2012-03-28 4:41 ` [Qemu-devel] [PATCH 2/4] Added a pci_region_entry structure Alexey Korolev
2012-03-28 4:54 ` [Qemu-devel] [PATCH 3/4] Switch from array based resource allocation to list Alexey Korolev
2012-04-01 7:28 ` Kevin O'Connor
2012-04-01 8:44 ` Kevin O'Connor
2012-04-03 6:39 ` Alexey Korolev
2012-04-04 3:31 ` Kevin O'Connor
2012-03-28 4:56 ` [Qemu-devel] [PATCH 4/4] Get rid of size element of pci_bus->r structure Alexey Korolev
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=4F73C2FF.5000709@endace.com \
--to=alexey.korolev@endace.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=sfd@endace.com \
/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).