From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 3] xl: carry domain config around in struct domain_config
Date: Mon, 26 Jul 2010 13:20:32 +0100 [thread overview]
Message-ID: <patchbomb.1280146832@localhost.localdomain> (raw)
Move more domain configuration items into struct domain_config.
Reduces the number of functions which take large numbers of parameters
and generally just keeps configuration stuff in one place.
next reply other threads:[~2010-07-26 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 12:20 Ian Campbell [this message]
2010-07-26 12:20 ` [PATCH 1 of 3] xl: move create and build info to struct domain_config Ian Campbell
2010-07-26 12:20 ` [PATCH 2 of 3] xl: move device structs into " Ian Campbell
2010-07-26 12:20 ` [PATCH 3 of 3] xl: simplify configuration parsing with local variables Ian Campbell
2010-07-26 14:40 ` [PATCH 0 of 3] xl: carry domain config around in struct domain_config Stefano Stabellini
2010-07-26 14:44 ` Ian Campbell
2010-07-26 15:03 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2010-07-27 10:28 Ian Campbell
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=patchbomb.1280146832@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=xen-devel@lists.xensource.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).