From: Ari Sundholm <ari@tuxera.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qapi/block-core.json: Add missing documentation for blklogwrites log-append option
Date: Mon, 9 Jul 2018 14:17:27 +0300 [thread overview]
Message-ID: <fcebd6aa-6346-35d8-cedf-71f5677033e7@tuxera.com> (raw)
In-Reply-To: <87lgakopio.fsf@dusky.pond.sub.org>
On 07/09/2018 10:07 AM, Markus Armbruster wrote:
> Ari Sundholm <ari@tuxera.com> writes:
>
>> This was accidentally omitted. Thanks to Eric Blake for spotting this.
>>
>> Signed-off-by: Ari Sundholm <ari@tuxera.com>
>> ---
>> qapi/block-core.json | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>> index 38b3125..62a92fa 100644
>> --- a/qapi/block-core.json
>> +++ b/qapi/block-core.json
>> @@ -3057,6 +3057,8 @@
>> # @log-sector-size: sector size used in logging writes to @file, determines
>> # granularity of offsets and sizes of writes (default: 512)
>> #
>> +# @log-append: append to an existing log (default: false)
>> +#
>> # @log-super-update-interval: interval of write requests after which the log
>> # super block is updated to disk (default: 4096)
>> #
>
> Applied to qapi-next. Thanks!
>
Thanks. Does this mean that the patch be queued for 3.0 or should I take
some additional steps to ensure this?
next prev parent reply other threads:[~2018-07-09 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 12:21 [Qemu-devel] [PATCH] qapi/block-core.json: Add missing documentation for blklogwrites log-append option Ari Sundholm
2018-07-06 19:37 ` Eric Blake
2018-07-09 7:07 ` Markus Armbruster
2018-07-09 11:17 ` Ari Sundholm [this message]
2018-07-10 5:28 ` 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=fcebd6aa-6346-35d8-cedf-71f5677033e7@tuxera.com \
--to=ari@tuxera.com \
--cc=armbru@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).