From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PULL 0/3] Machine queue, 2021-02-02
Date: Wed, 3 Feb 2021 12:55:26 +0000 [thread overview]
Message-ID: <CAFEAcA-D_CyFrTyDX1qHA21fTaJ2Nh0h9jPjQcMYGgJAL4MO0Q@mail.gmail.com> (raw)
In-Reply-To: <20210202193020.4107711-1-ehabkost@redhat.com>
On Tue, 2 Feb 2021 at 19:31, Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> I still have a huge list of patches to review, but I don't keep
> this series stuck in the queue while I try to catch up.
>
> The following changes since commit 74208cd252c5da9d867270a178799abd802b9338:
>
> Merge remote-tracking branch 'remotes/berrange-gitlab/tags/misc-fixes-pull-request' into staging (2021-01-29 19:51:25 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/ehabkost/qemu.git tags/machine-next-pull-request
>
> for you to fetch changes up to dbd730e8598701e11b2fb7aee1704f4ec1787e86:
>
> nvdimm: check -object memory-backend-file, readonly=on option (2021-02-01 17:07:34 -0500)
>
> ----------------------------------------------------------------
> Machine queue, 2021-02-02
>
> Feature:
> * nvdimm: read-only file support (Stefan Hajnoczi)
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-02-03 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:30 [PULL 0/3] Machine queue, 2021-02-02 Eduardo Habkost
2021-02-02 19:30 ` [PULL 1/3] memory: add readonly support to memory_region_init_ram_from_file() Eduardo Habkost
2021-02-02 19:30 ` [PULL 2/3] hostmem-file: add readonly=on|off option Eduardo Habkost
2021-02-02 19:30 ` [PULL 3/3] nvdimm: check -object memory-backend-file, readonly=on option Eduardo Habkost
2021-02-03 12:55 ` Peter Maydell [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=CAFEAcA-D_CyFrTyDX1qHA21fTaJ2Nh0h9jPjQcMYGgJAL4MO0Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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).