From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] Machine queue, 2019-01-28
Date: Mon, 28 Jan 2019 17:43:49 -0200 [thread overview]
Message-ID: <20190128194351.14679-1-ehabkost@redhat.com> (raw)
The following changes since commit 5f39a91dbd9a186edb999afd4d17524f4b1da14f:
Merge remote-tracking branch 'remotes/jnsnow/tags/ide-pull-request' into staging (2019-01-28 12:54:06 +0000)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
for you to fetch changes up to 21d1683690e048663855dd6feb3034ab7c5039bc:
hostmem: add more information in error messages (2019-01-28 15:52:05 -0200)
----------------------------------------------------------------
Machine queue, 2019-01-28
* Fix small leak on NUMA code
* Improve memory backend error messages
----------------------------------------------------------------
Queue for Machine Core patches
Zhang Yi (2):
numa: Fixed the memory leak of numa error message
hostmem: add more information in error messages
backends/hostmem-file.c | 6 ++++--
backends/hostmem.c | 8 +++++---
numa.c | 1 +
3 files changed, 10 insertions(+), 5 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-01-28 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 19:43 Eduardo Habkost [this message]
2019-01-28 19:43 ` [Qemu-devel] [PULL 1/2] numa: Fixed the memory leak of numa error message Eduardo Habkost
2019-01-28 19:43 ` [Qemu-devel] [PULL 2/2] hostmem: add more information in error messages Eduardo Habkost
2019-01-31 12:03 ` [Qemu-devel] [PULL 0/2] Machine queue, 2019-01-28 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=20190128194351.14679-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).