From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: pkrempa@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] file-posix: Add dynamic-auto-read-only QAPI feature
Date: Fri, 7 Jun 2019 17:02:55 +0200 [thread overview]
Message-ID: <20190607150255.GG5055@dhcp-200-226.str.redhat.com> (raw)
In-Reply-To: <20190606153803.5278-1-armbru@redhat.com>
Am 06.06.2019 um 17:37 hat Markus Armbruster geschrieben:
> This series adds optional feature lists to struct definitions in the
> QAPI schema and makes use of them to advertise the new behaviour of
> auto-read-only=on in file-posix.
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2019-06-07 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 15:37 [Qemu-devel] [PATCH 0/7] file-posix: Add dynamic-auto-read-only QAPI feature Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 1/7] qapi: Add feature flags to struct types Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 2/7] tests/qapi-schema: Test for good feature lists in structs Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 3/7] tests/qapi-schema: Error case tests for features " Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 4/7] qapi: Disentangle QAPIDoc code Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 5/7] qapi: Allow documentation for features Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 6/7] file-posix: Add dynamic-auto-read-only QAPI feature Markus Armbruster
2019-06-06 15:54 ` Eric Blake
2019-06-12 16:31 ` Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 7/7] qapi: Simplify QAPIDoc implements its state machine Markus Armbruster
2019-06-07 15:02 ` Kevin Wolf [this message]
2019-06-12 16:45 ` [Qemu-devel] [PATCH 0/7] file-posix: Add dynamic-auto-read-only QAPI feature Markus Armbruster
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=20190607150255.GG5055@dhcp-200-226.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=pkrempa@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).