From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/1] fw_cfg: unbreak migration compatibility for 2.4 and earlier machines
Date: Mon, 29 Feb 2016 10:53:57 +0100 [thread overview]
Message-ID: <1456739638-20903-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
fwcfg acpi series which I planned to include here is blocked by unexpected
apci test behavior. So I'm sending this patch alone so it doesn't has to
wait until our acpi experts figured what is going on (and maybe the
fwcfg acpi series then goes through the acpi queue anyway).
please pull,
Gerd
The following changes since commit 0c6940d086f39bbf725d96104abe46da87429cb6:
build: [bsd-user] Rename "syscall.h" to "target_syscall.h" in target directories (2016-02-25 16:41:08 +0000)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-fw-cfg-20160226-1
for you to fetch changes up to e6915b5f3a874a467a9a65f7ec1d6ef8d251a51a:
fw_cfg: unbreak migration compatibility for 2.4 and earlier machines (2016-02-26 10:06:40 +0100)
----------------------------------------------------------------
fw_cfg: unbreak migration compatibility for 2.4 and earlier machines
----------------------------------------------------------------
Laszlo Ersek (1):
fw_cfg: unbreak migration compatibility for 2.4 and earlier machines
hw/nvram/fw_cfg.c | 20 ++++++++++++--------
include/hw/compat.h | 8 ++++++++
2 files changed, 20 insertions(+), 8 deletions(-)
next reply other threads:[~2016-02-29 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 9:53 Gerd Hoffmann [this message]
2016-02-29 9:53 ` [Qemu-devel] [PULL 1/1] fw_cfg: unbreak migration compatibility for 2.4 and earlier machines Gerd Hoffmann
2016-02-29 11:49 ` [Qemu-devel] [PULL 0/1] " Peter Maydell
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=1456739638-20903-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).