From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/8] Misc patches for QEMU 5.0-rc3
Date: Tue, 14 Apr 2020 09:36:50 +0200 [thread overview]
Message-ID: <20200414093650.62ff8502@redhat.com> (raw)
In-Reply-To: <20200411130330.1993-1-pbonzini@redhat.com>
On Sat, 11 Apr 2020 09:03:22 -0400
Paolo Bonzini <pbonzini@redhat.com> wrote:
> The following changes since commit 53ef8a92eb04ee19640f5aad3bff36cd4a36c250:
>
> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20200406' into staging (2020-04-06 12:36:45 +0100)
>
> are available in the Git repository at:
>
> git://github.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to 8c12bd8e32faf8c483cd96c1557899120bc67eea:
>
> module: increase dirs array size by one (2020-04-11 08:49:26 -0400)
>
> ----------------------------------------------------------------
> Bugfixes, and reworking of the atomics documentation.
>
> ----------------------------------------------------------------
> Alexander Duyck (1):
> memory: Do not allow direct write access to rom_device regions
>
> Bauerchen (1):
> oslib-posix: take lock before qemu_cond_broadcast
>
> Bruce Rogers (1):
> module: increase dirs array size by one
>
> Igor Mammedov (1):
> vl.c: error out if -mem-path is used together with -M memory-backend
It seems one more patch was forgotten
"[PATCH for-5.0 0/2] fix qemu crash with memory-backend-* prealloc=yes"
>
> Olaf Hering (1):
> piix: fix xenfv regression, add compat machine xenfv-4.2
>
> Paolo Bonzini (3):
> atomics: convert to reStructuredText
> atomics: update documentation
> rcu: do not mention atomic_mb_read/set in documentation
>
> docs/devel/atomics.rst | 507 +++++++++++++++++++++++++++++++++++
> docs/devel/atomics.txt | 403 ----------------------------
> docs/devel/index.rst | 1 +
> docs/devel/rcu.txt | 4 +-
> hw/i386/pc_piix.c | 19 +-
> include/exec/memory.h | 4 +-
> roms/SLOF | 2 +-
> softmmu/vl.c | 5 +
> tests/qtest/device-introspect-test.c | 2 +-
> tests/qtest/qom-test.c | 42 +--
> tests/qtest/test-hmp.c | 2 +-
> util/module.c | 2 +-
> util/oslib-posix.c | 3 +
> 13 files changed, 548 insertions(+), 448 deletions(-)
> create mode 100644 docs/devel/atomics.rst
> delete mode 100644 docs/devel/atomics.txt
prev parent reply other threads:[~2020-04-14 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 13:03 [PULL 0/8] Misc patches for QEMU 5.0-rc3 Paolo Bonzini
2020-04-11 13:03 ` [PULL 1/8] piix: fix xenfv regression, add compat machine xenfv-4.2 Paolo Bonzini
2020-04-11 13:03 ` [PULL 2/8] oslib-posix: take lock before qemu_cond_broadcast Paolo Bonzini
2020-04-11 13:03 ` [PULL 3/8] atomics: convert to reStructuredText Paolo Bonzini
2020-04-11 13:03 ` [PULL 4/8] atomics: update documentation Paolo Bonzini
2020-04-11 13:03 ` [PULL 5/8] rcu: do not mention atomic_mb_read/set in documentation Paolo Bonzini
2020-04-11 13:03 ` [PULL 6/8] vl.c: error out if -mem-path is used together with -M memory-backend Paolo Bonzini
2020-04-11 13:03 ` [PULL 7/8] memory: Do not allow direct write access to rom_device regions Paolo Bonzini
2020-04-11 13:03 ` [PULL 8/8] module: increase dirs array size by one Paolo Bonzini
2020-04-11 16:54 ` [PULL 0/8] Misc patches for QEMU 5.0-rc3 Peter Maydell
2020-04-14 7:36 ` Igor Mammedov [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=20200414093650.62ff8502@redhat.com \
--to=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).