From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL v5 00/42] Block layer patches and object-add QAPIfication
Date: Fri, 19 Mar 2021 15:05:07 +0100 [thread overview]
Message-ID: <YFSvk41vwGuEG/Hn@merkur.fritz.box> (raw)
In-Reply-To: <CAFEAcA-R2MuuaVhwyWxAhMyWNG5jPZTwqs6bKe97O+5Ertr2cg@mail.gmail.com>
Am 19.03.2021 um 14:34 hat Peter Maydell geschrieben:
> On Fri, 19 Mar 2021 at 09:20, Kevin Wolf <kwolf@redhat.com> wrote:
> >
> > The following changes since commit 8a40754bca14df63c6d2ffe473b68a270dc50679:
> >
> > Merge remote-tracking branch 'remotes/nvme/tags/nvme-next-pull-request' into staging (2021-03-18 19:55:37 +0000)
> >
> > are available in the Git repository at:
> >
> > git://repo.or.cz/qemu/kevin.git tags/for-upstream
> >
> > for you to fetch changes up to 009ff89328b1da3ea8ba316bf2be2125bc9937c5:
> >
> > vl: allow passing JSON to -object (2021-03-19 10:18:17 +0100)
> >
> > ----------------------------------------------------------------
> > Block layer patches and object-add QAPIfication
> >
> > - QAPIfy object-add and --object
> > - stream: Fail gracefully if permission is denied
> > - storage-daemon: Fix crash on quit when job is still running
> > - curl: Fix use after free
> > - char: Deprecate backend aliases, fix QMP query-chardev-backends
> > - Fix image creation option defaults that exist in both the format and
> > the protocol layer (e.g. 'cluster_size' in qcow2 and rbd; the qcow2
> > default was incorrectly applied to the rbd layer)
>
> Applied, thanks.
Hallelujah!
I was already worried about making the hard freeze even though I had
sent v1 well before soft freeze. :-)
Kevin
prev parent reply other threads:[~2021-03-19 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 9:20 [PULL v5 00/42] Block layer patches and object-add QAPIfication Kevin Wolf
2021-03-19 13:34 ` Peter Maydell
2021-03-19 14:05 ` Kevin Wolf [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=YFSvk41vwGuEG/Hn@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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).