From: Peter Maydell <peter.maydell@linaro.org>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/5] Block patches for 4.2-rc0
Date: Wed, 6 Nov 2019 11:56:03 +0000 [thread overview]
Message-ID: <CAFEAcA-fDZ7bb=88KbdmTcBWRhua_A66a41E9kr9O3AMWVbCmw@mail.gmail.com> (raw)
In-Reply-To: <20191104090347.27278-1-mreitz@redhat.com>
On Mon, 4 Nov 2019 at 09:03, Max Reitz <mreitz@redhat.com> wrote:
>
> The following changes since commit 36609b4fa36f0ac934874371874416f7533a5408:
>
> Merge remote-tracking branch 'remotes/palmer/tags/palmer-for-master-4.2-sf1' into staging (2019-11-02 17:59:03 +0000)
>
> are available in the Git repository at:
>
> https://github.com/XanClic/qemu.git tags/pull-block-2019-11-04
>
> for you to fetch changes up to 292d06b925b2787ee6f2430996b95651cae42fce:
>
> block/file-posix: Let post-EOF fallocate serialize (2019-11-04 09:33:51 +0100)
>
> ----------------------------------------------------------------
> Block patches for 4.2-rc0:
> - Work around XFS write-zeroes bug in file-posix block driver
> - Fix backup job with compression
> - Fix to the NVMe block driver header
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-11-06 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 9:03 [PULL 0/5] Block patches for 4.2-rc0 Max Reitz
2019-11-04 9:03 ` [PULL 1/5] nvme: fix NSSRS offset in CAP register Max Reitz
2019-11-04 9:03 ` [PULL 2/5] block/block-copy: fix s->copy_size for compressed cluster Max Reitz
2019-11-04 9:03 ` [PULL 3/5] block: Make wait/mark serialising requests public Max Reitz
2019-11-04 9:03 ` [PULL 4/5] block: Add bdrv_co_get_self_request() Max Reitz
2019-11-04 9:03 ` [PULL 5/5] block/file-posix: Let post-EOF fallocate serialize Max Reitz
2019-11-06 11:56 ` 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-fDZ7bb=88KbdmTcBWRhua_A66a41E9kr9O3AMWVbCmw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).