From: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
To: Daniel Kiper <dkiper-lGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
Cc: olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org,
xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org,
konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 0/4] kexec-tools: Xen fixes and cleanups
Date: Mon, 22 Aug 2011 07:47:38 +0900 [thread overview]
Message-ID: <20110821224737.GF2300@verge.net.au> (raw)
In-Reply-To: <20110821135029.GA17323-AmBulhRT4w7qC4U/RHarzn2k5y3jIR3H/ehkLePY6aQ@public.gmane.org>
On Sun, Aug 21, 2011 at 03:50:29PM +0200, Daniel Kiper wrote:
> Hi,
>
> I am sending some Xen specific fixes and cleanups for kexec-tools.
> These patches applies to current kexec-tools git tree.
>
> Full list of fixes and cleanups:
> - xen: Take into account Xen control interface changes since Xen Ver. 4.1,
> - kexec: Export compare_ranges() function from firmware_memmap.c module,
> - kexec/arch/i386: Rename fixup_memory_ranges_sysfs() to fixup_memory_ranges(),
> - kexec/arch/i386: Add get_memory_ranges_xen() function.
Thanks Daniel,
all applied.
prev parent reply other threads:[~2011-08-21 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 13:50 [PATCH 0/4] kexec-tools: Xen fixes and cleanups Daniel Kiper
[not found] ` <20110821135029.GA17323-AmBulhRT4w7qC4U/RHarzn2k5y3jIR3H/ehkLePY6aQ@public.gmane.org>
2011-08-21 22:47 ` Simon Horman [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=20110821224737.GF2300@verge.net.au \
--to=horms-/r6kz+ddxgppr4jqbcensq@public.gmane.org \
--cc=dkiper-lGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org \
--cc=ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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).