From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, Dario Faggioli <raistlin@linux.it>
Subject: [PATCH 0 of 4 V2] xl: guest reboot cleanups
Date: Fri, 29 Jun 2012 09:14:07 +0100 [thread overview]
Message-ID: <patchbomb.1340957647@cosworth.uk.xensource.com> (raw)
These are miscellaneous fixes I noticed while tracking down the guest
reboot failures in light 13302, previously posted as 'xl: fix guest
reboot failures'.
The reboot issue is already fixed but these remained outstanding. I've
rebased to current tip and fixed the trivial conflict in cpupool_info.
next reply other threads:[~2012-06-29 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 8:14 Ian Campbell [this message]
2012-06-29 8:14 ` [PATCH 1 of 4 V2] libxl: initialise cpupoolinfo in libxl__domain_scheduler Ian Campbell
2012-06-29 8:14 ` [PATCH 2 of 4 V2] libxl: correct type of cpupool variable Ian Campbell
2012-06-29 8:14 ` [PATCH 3 of 4 V2] libxl: log on failure in cpupool_info and libxl__domain_cpupool Ian Campbell
2012-06-29 8:14 ` [PATCH 4 of 4 V2] xl: initialise domid to an explicitly invalid value 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.1340957647@cosworth.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=raistlin@linux.it \
--cc=xen-devel@lists.xen.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).