From: Andrew Cooper <andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: Daniel Kiper <daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
kumagai-atsushi-biTfD1RFvDe45+QrQBaojngSJqDPrsil@public.gmane.org
Subject: Re: [Xen-devel] [PATCH 0/7] Xen fixes and minor cleanups
Date: Fri, 12 Jul 2013 15:01:22 +0100 [thread overview]
Message-ID: <51E00C32.6090204@citrix.com> (raw)
In-Reply-To: <1373636895-31682-1-git-send-email-daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On 12/07/13 14:48, Daniel Kiper wrote:
> Hi,
>
> This patch series contains following Xen fixes and cleanups:
> - xen: Improve calculation of beginning of virtual address space,
> - elf: Increase buf size in get_pt_note_info(),
> - xen: Take into account new frame table address since Xen 4.3,
> - xen: Enforce page size only when xen-syms file is used,
> - Mute some compiler warnings,
> - Use elf_getshdrstrndx() instead of elf_getshstrndx(),
> - Do not break progress messages.
>
> All patches were tested with Xen versions up to 4.3.
>
> Daniel
I presume these are all kexec-tools fixes, given the files patched, but
no specific statement one way or another?
~Andrew
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel-GuqFBffKawuEi8DpZVb4nw@public.gmane.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-07-12 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 13:48 [PATCH 0/7] Xen fixes and minor cleanups Daniel Kiper
[not found] ` <1373636895-31682-1-git-send-email-daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-07-12 13:48 ` [PATCH 1/7] xen: Improve calculation of beginning of virtual address space Daniel Kiper
2013-07-12 13:48 ` [PATCH 2/7] elf: Increase buf size in get_pt_note_info() Daniel Kiper
[not found] ` <1373636895-31682-3-git-send-email-daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-07-12 14:04 ` [Xen-devel] " Andrew Cooper
[not found] ` <51E00CF9.7080604-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2013-07-12 19:09 ` Daniel Kiper
2013-07-12 13:48 ` [PATCH 3/7] xen: Take into account new frame table address since Xen 4.3 Daniel Kiper
2013-07-12 13:48 ` [PATCH 4/7] xen: Enforce page size only when xen-syms file is used Daniel Kiper
2013-07-12 13:48 ` [PATCH 5/7] Mute some compiler warnings Daniel Kiper
[not found] ` <1373636895-31682-6-git-send-email-daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-07-12 14:12 ` [Xen-devel] " Andrew Cooper
2013-07-12 13:48 ` [PATCH 6/7] Use elf_getshdrstrndx() instead of elf_getshstrndx() Daniel Kiper
2013-07-12 13:48 ` [PATCH 7/7] Do not break progress messages Daniel Kiper
2013-07-12 14:01 ` Andrew Cooper [this message]
[not found] ` <51E00C32.6090204-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2013-07-12 14:30 ` [Xen-devel] [PATCH 0/7] Xen fixes and minor cleanups Daniel Kiper
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=51E00C32.6090204@citrix.com \
--to=andrew.cooper3-sxgqhf6nn4dqt0dzr+alfa@public.gmane.org \
--cc=daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=kumagai-atsushi-biTfD1RFvDe45+QrQBaojngSJqDPrsil@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).